Preparing for the Strategy Project

6.1 Clarifying the Sponsor, Mandate, Decision Rights, and Intended Use

The first preparation task is to clarify sponsorship. In culture sector projects, sponsorship is often more complicated than it appears. A mayor, minister, governor, foundation president, economic development corporation, cultural agency, or tourism authority may announce the strategy, but another body may control the budget, data, assets, or implementation. If sponsorship is ambiguous, the project team may complete a technically sound strategy that no one is positioned to execute.

Sponsor: the sponsor is the person or institution accountable for commissioning the strategy, resolving major issues, and ensuring the work is used. The sponsor does not need to make every technical decision, but must have enough authority to convene stakeholders, request data, approve scope, and carry recommendations into the relevant budget, policy, or governance process. A project champion is helpful, but a champion without authority is not a sponsor.

Mandate: the mandate defines why the project exists and what it is authorized to examine. A good mandate explains the problem, the opportunity, the geography, the cultural domains in scope, the institutional boundaries, and the expected decisions. It should also say whether the project is a first-phase diagnostic, a full strategy, a funding review, a creative economy plan, a cultural tourism alignment exercise, or an implementation roadmap. Without this clarity, stakeholders will project their own expectations onto the work.

Decision rights: decision rights specify who can approve scope, methodology, stakeholder engagement plans, interim findings, benchmark selection, strategic priorities, initiative recommendations, and the final report. These rights should be explicit before the kickoff. Culture sector strategies often involve many agencies and funders, and the absence of decision rights can create late-stage conflict. A steering committee may review recommendations, but the project still needs a clear final decision maker.

Intended use: the intended use explains how the strategy will be applied after completion. It may inform annual budgets, grant reform, capital investment, institutional mandates, cultural district planning, tourism alignment, creative industry support, philanthropic priorities, or economic development programming. A strategy intended to support a cabinet decision will be structured differently from one intended to guide a foundation portfolio. A strategy intended to create a public vision will differ from a confidential diagnostic for a development corporation.

Intended use should be stated in plain language, because it will influence the level of detail required. A report intended to support a funding realignment must include enough evidence to justify changes in grant criteria. A report intended to guide capital investment must include facility conditions, demand evidence, operating implications, and sequencing. A report intended to support sector advocacy may emphasize narrative and economic contribution. A report intended to support implementation should include initiative owners, dependencies, budget ranges, and governance recommendations. The same subject can produce very different deliverables depending on intended use.

The sponsor should also confirm the audience for the work. Some strategies are written primarily for executive decision makers. Others must be credible to artists, community groups, cultural institutions, funders, tourism bodies, investors, and residents. A strategy for public release requires different language, evidence presentation, and engagement discipline than a confidential diagnostic. Misalignment on the audience often creates late-stage rewriting, because the team discovers too late that the document was designed for one use but needed for another.

The project team should create a short project charter during mobilization. The charter should not be a long administrative document. It should answer the questions that will shape the work: who owns the strategy, what decisions it will inform, what is in scope, what is out of scope, which stakeholders must be involved, what deliverables are expected, and what implementation pathway is realistic. The charter is also the first place to document constraints, such as limited data availability, political sensitivities, compressed timelines, or dependencies on another policy process.

The most common preparation failure is confusing interest with accountability. Many stakeholders may care about the strategy. Fewer will own its consequences. The project should be designed around those who can use the work, while still engaging those who will be affected by it.

6.2 Establishing the Project Governance Model

A culture sector strategy needs governance that is light enough to move quickly and strong enough to make decisions. Too little governance leaves the project exposed to drift, data delays, and late-stage objections. Too much governance turns the work into a sequence of meetings where every stakeholder can slow progress but no one can decide. The objective is not to build a bureaucracy around the project. It is to create a structure that allows evidence, judgment, and accountability to come together.

Executive sponsor: the executive sponsor provides authority and ensures the strategy remains connected to the decisions it is meant to influence. This person should chair or appoint the chair of the main steering forum, unblock access to agencies, and make final calls when trade-offs arise. The sponsor’s visible involvement signals that the work is not merely a consultation exercise.

Project director: the project director manages the day-to-day work on behalf of the sponsor. This role coordinates the internal team, external advisors, data owners, stakeholder engagement, and deliverable review. The project director should be senior enough to command cooperation but close enough to the work to resolve practical issues quickly.

Core working team: the core team conducts analysis, manages data, prepares materials, schedules engagement, drafts findings, and maintains the issue log. It usually includes strategy, culture, economic development, tourism, data, finance, and communications representatives, depending on scope. The core team should meet frequently and operate with clear responsibilities.

Steering committee: the steering committee reviews direction, validates major findings, resolves cross-agency tensions, and approves key deliverables. It should include decision makers, not only observers. A steering committee that is too large may become symbolic. A smaller committee with authority, supported by broader advisory engagement, is usually more effective.

Advisory group: an advisory group can provide field knowledge, community perspective, sector credibility, and challenge. It may include cultural leaders, artists, creative entrepreneurs, heritage experts, educators, funders, community representatives, tourism bodies, and economic development partners. The advisory group should inform the work, not serve as the final approval body unless that is explicitly intended.

The governance model should be documented in a one-page operating model. It should show the role of each forum, meeting frequency, inputs, outputs, and decisions expected. This is especially useful when external advisors are involved, because it prevents confusion between consultant recommendations, internal team judgment, advisory group feedback, and sponsor approval. Clear governance does not make the process less collaborative. It makes collaboration productive by showing where input is welcomed and where decisions must be made.

The governance model should also define escalation. Data gaps, scope disputes, stakeholder complaints, politically sensitive findings, and competing agency priorities should not linger unresolved. A simple escalation path from workstream lead to project director to executive sponsor prevents avoidable delays. The project should maintain a decision log so changes to scope, methodology, benchmarks, or deliverables are recorded rather than rediscovered later.

6.3 Defining the Workplan, Timeline, Milestones, and Review Forums

Once sponsorship and governance are clear, the team should define the workplan. The workplan is more than a schedule. It is the logic of how the strategy will be built. It should show how the project will move from mobilization to evidence gathering, from evidence to diagnosis, from diagnosis to strategic choices, and from choices to deliverables that can be approved and used.

A typical culture sector strategy project has several phases. Mobilization: confirms scope, governance, stakeholders, data requirements, and the project charter. Current-state assessment: maps assets, analyzes funding, reviews institutions, examines participation, estimates economic contribution, and identifies baseline sector conditions. Stakeholder engagement: gathers insight from cultural organizations, artists, communities, agencies, visitors, funders, businesses, and anchor institutions. Benchmarking: compares the place or portfolio with relevant peers and extracts transferable lessons. Diagnosis: identifies gaps, constraints, underperformance, strengths, and opportunities. Strategy development: defines the vision, objectives, priorities, initiatives, governance implications, funding model, and roadmap. Finalization: tests recommendations, resolves decisions, prepares the final deliverable, and plans launch or implementation.

The timeline depends on scope. A narrow first-phase project focused on benchmarking and current-state analysis may be completed in six to ten weeks if data is available and stakeholders are aligned. A full culture sector strategy for a city or region often requires twelve to twenty weeks. A national or statewide strategy, especially one involving extensive community engagement, Indigenous consultation, or major economic analysis, may require longer. Compressing the timeline can be appropriate, but only if the sponsor accepts trade-offs in engagement depth, data validation, or initiative design.

Milestones: milestones should be tied to decisions, not merely activity completion. Useful milestones include project charter approval, data request release, stakeholder map approval, benchmark selection, current-state fact base review, engagement findings review, gap-analysis sign-off, strategic options workshop, initiative prioritization, implementation roadmap review, and final deliverable approval. Each milestone should specify the decision required, the materials needed, and the approver.

Review forums: review forums should match the rhythm of the work. The core team may meet weekly or twice weekly during data-heavy periods. The project director and consulting team may hold short working sessions more often. The steering committee may meet at major gates. Advisory groups may meet at the beginning, middle, and near-final stages. Public workshops or listening sessions may be scheduled after the team has enough context to ask focused questions but before recommendations are locked.

Workplans should also define how outputs will be developed. Some teams wait until the end to begin drafting the final document, which creates unnecessary pressure and often produces a report that reads like assembled workstreams. A better approach is to build the deliverable progressively. The asset map, benchmark findings, current-state assessment, gap analysis, strategic options, initiative portfolio, and implementation roadmap should each be drafted, tested, and refined as the project proceeds. By the time the final report is assembled, the main arguments should already have been reviewed.

The workplan should also include buffer time. Culture sector projects involve data delays, stakeholder sensitivities, and interpretation challenges. Asset lists may be incomplete. Survey response rates may be low. Economic data may not align with cultural definitions. Community meetings may raise issues outside the original scope. Benchmarks may not be directly comparable. A realistic workplan assumes iteration rather than pretending the project will move in a straight line.

6.4 Building the Initial Data Request

The initial data request is one of the most important preparation tools. It signals what kind of evidence the strategy will use and reveals how ready the sponsor is to support rigorous analysis. A weak data request produces a weak baseline. A vague request produces delays. An overly broad request overwhelms agencies and cultural organizations. The right data request is specific, sequenced, and tied to the strategic questions.

The project team should begin by identifying the analyses required. If the strategy needs an economic contribution estimate, the team will need employment, revenue, wage, business, tourism, and expenditure data. If the strategy needs a funding review, the team will need grant records, operating budgets, capital allocations, eligibility criteria, and reporting data. If the strategy needs asset mapping, it will need lists of venues, institutions, heritage sites, festivals, public art, creative workspaces, cultural districts, and community organizations. If the strategy needs an access analysis, it will need geography, participation, demographics, transport, pricing, and facility data.

Data ownership: every requested dataset should have an owner. One of the most common causes of delay is requesting data from a department that does not control it. The data request should name the agency, team, or individual responsible for each source and define the expected format, delivery date, confidentiality level, and known limitations.

Data quality: data should be reviewed for completeness, comparability, timeliness, and consistency. Cultural data is often messy. Grant categories may have changed over time. Organizations may report attendance differently. Employment codes may not capture freelancers. Visitor surveys may not distinguish cultural motivations. Asset inventories may mix active institutions with inactive listings. The team should document limitations early so findings are not overstated later.

The data request should be accompanied by a data tracker. The tracker should record the dataset name, owner, request date, due date, status, format, confidentiality level, quality issues, and analytical use. This small discipline prevents confusion when dozens of files arrive from different agencies. It also helps the project team identify gaps early. If employment data, attendance data, or funding records are missing, the team can decide whether to use proxies, launch a survey, conduct interviews, or adjust the scope of analysis.

Confidentiality: some data will be sensitive. Cultural organizations may provide financial statements, payroll estimates, attendance figures, donor information, lease terms, or operating challenges. Creative businesses may share revenue, employment, or investment data. The project should define how sensitive data will be handled, aggregated, anonymized, and reported. Trust in the data process affects response quality.

A practical initial data request often includes the following categories:

• Strategy and policy documents: existing culture plans, arts policies, heritage policies, tourism strategies, economic development strategies, district plans, education strategies, and major capital plans.
• Funding and budget data: grant programs, operating support, capital allocations, sponsorships, foundation funding, eligibility rules, award histories, and reporting requirements.
• Asset and institution data: museums, galleries, theaters, libraries, archives, heritage sites, festivals, venues, studios, public art, cultural centers, creative workspaces, and community organizations.
• Economic and employment data: business counts, employment, wages, revenues, occupational data, creative industry classifications, freelancer estimates, supplier spending, and tourism expenditure where available.
• Participation and audience data: attendance, ticketing, memberships, school visits, visitor origins, participation surveys, demographic data, accessibility indicators, and geographic distribution.
• Infrastructure and capital data: facility condition, utilization, ownership, maintenance backlog, planned investments, leases, capacity, equipment, and accessibility compliance.
• Governance and operating data: agency mandates, organizational charts, board structures, service agreements, contracts, performance reports, and interagency working arrangements.

The data request should be staged. The first wave should focus on documents and datasets needed to build the baseline. The second wave can address gaps that emerge from initial analysis. The third wave may support initiative design, costing, or implementation planning. This sequencing prevents the team from asking for everything at once and allows data owners to respond intelligently.

6.5 Project Readiness Checklist

Before launching interviews, surveys, workshops, or public communications, the sponsor should confirm that the project is ready. Readiness does not mean every issue has been solved. It means the project has enough clarity, authority, evidence access, and governance to proceed without creating avoidable confusion.

A practical readiness checklist should cover the following tests:

• Sponsor test: an accountable sponsor has been identified and is prepared to resolve major issues.
• Mandate test: the project purpose, scope, intended use, and expected deliverables are documented.
• Decision-rights test: the team knows who approves scope, methodology, findings, recommendations, and final outputs.
• Governance test: the executive sponsor, project director, core team, steering committee, advisory group, and escalation route are defined.
• Workplan test: phases, milestones, review forums, and decision gates are mapped against a realistic timeline.
• Data test: the initial data request has been issued, data owners are named, and confidentiality rules are understood.
• Stakeholder test: the initial stakeholder map identifies agencies, cultural institutions, artists, community groups, funders, creative businesses, and other affected parties.
• Communications test: the team has agreed how the project will be described publicly and how expectations will be managed.
• Implementation test: there is a plausible pathway from the final strategy to funding, governance, programs, or policy action.

If several tests fail, the sponsor should consider a short mobilization phase before beginning the full strategy. This is not a delay for its own sake. It is a way to prevent rework, stakeholder frustration, and weak recommendations. A two-week mobilization effort can save months of confusion by confirming scope, governance, data availability, and engagement protocols.

The readiness checklist should be revisited at each major gate. A project may begin with enough clarity but encounter new questions as evidence emerges. The mandate may need refinement. The stakeholder map may need expansion. A data gap may require a survey. A governance issue may require escalation. Readiness is not a one-time administrative step; it is a continuing discipline.

Preparation is sometimes invisible in the final report, but it is highly visible in the quality of the work. Well-prepared projects have clearer findings, more credible engagement, stronger recommendations, and a better chance of implementation. Poorly prepared projects spend their energy correcting misunderstandings that should have been resolved before the first interview. For a culture sector strategy, the first deliverable is not the final document. It is the conditions for making the final document useful.