Learning path · Level 10 · Tutorial 2

Build a Capacity-Aware Marketing Roadmap

Turn the integrated plan into a phased roadmap with owners, dependencies, cash budgets, and realistic workload estimates. Use a compact text table to compare feasible execution scenarios and explain what changes when resources or assumptions change.

  • Level: Advanced
  • Duration: 25 min
  • 8 steps
Start tutorial Back to the path
Build a Capacity-Aware Marketing Roadmap

What you will go through

  1. Turn the Integrated Plan into Executable Work Translate the carried-forward FocusFlow strategy into bounded work packages without introducing unsupported channel activity. 2 min
  2. Sequence Dependencies and Readiness Gates Sequence FocusFlow work through Prepare, Activate, and Optimize so shared assets, approvals, consent requirements, and measurement checks are ready before dependent activity launches. 3 min
  3. Make Ownership and Review Work Visible Assign clear ownership, visible review work, role-level effort, and actionable handoffs to FocusFlow roadmap packages. 3 min
  4. Resolve Weekly Capacity Bottlenecks Reconcile FocusFlow’s role-week workload against protected capacity, then repair a visible bottleneck while preserving dependencies, readiness, ownership, and handoffs. 3 min
  5. Build a Cash-and-Time Resource Budget Build the Resource budget section of the FocusFlow roadmap by keeping cash categories, timing, shared assets, and internal staff time visible and reconcilable. 3 min
  6. Make Forecasts Respect Time and Business Capacity Document a conditional FocusFlow forecast that respects readiness, channel timing, conversion lag, and the capacity to serve new customers. 3 min
  7. Compare Feasible Scenarios and Trade-offs Create a feasible constrained-resource scenario and justify what changes, what remains protected, and what is deferred. 4 min
  8. Finalize and Check Your Marketing Roadmap Assemble, audit, and preserve a feasible FocusFlow roadmap for the next stage of the integrated marketing-plan capstone. 4 min

What you will learn

  • Sequence activities into a phased roadmap, placing required assets, measurement checks, and approvals before dependent activities.
  • Assign accountable owners, review responsibilities, and effort estimates without exceeding stated team capacity.
  • Create a resource budget that distinguishes advertising spend, production and tool costs, and staff time while avoiding duplicated shared costs.
  • Document forecast assumptions and compare a base plan with a constrained-resource scenario, accounting for channel lead times and business capacity.
  • Justify which activities to protect, reduce, defer, or replace when a budget, capacity, or performance assumption changes.

Before you start

  • Connect Channels in an Integrated Marketing Plan
  • Choose Ad Bids and Budgets with Realistic Forecasts
  • Publishing calendars, production capacity, review ownership, and resource constraints.

Step 1 of 8

Turn the Integrated Plan into Executable Work

Translate the carried-forward FocusFlow strategy into bounded work packages without introducing unsupported channel activity.

1. Capture continuity, not a new strategy

Start with a fixed strategic core

This roadmap extends the integrated plan; it does not reopen strategy. If you do not have an earlier document available, use the complete FocusFlow case below. If you are continuing a learner-selected business, retain that business’s existing strategic core in the equivalent fields.

Start the cumulative artifact as FocusFlow roadmap. Its four sections are Continuity brief, Roadmap, Resource budget, and Scenarios and assumptions.

Use Carried forward for prior strategic decisions. Use Planning assumption for new operating figures that will constrain execution. A planning assumption can change the feasible delivery plan, but it does not authorize a new channel, audience, offer, or objective.

FocusFlow Continuity brief

This populated brief makes the case self-contained. It is a recap of the integrated plan, not an invitation to select channels again.

Copy these facts into the Continuity brief of your FocusFlow roadmap.
Brief elementCarried forward fact
AudienceOperations leads at small client-service teams that coordinate recurring client work.
OfferFocusFlow’s 14-day guided trial for planning recurring client work, with a setup consultation.
Objective and outcomeGenerate qualified trial requests for the guided trial. The primary conversion outcome is a qualified trial request; new-customer starts are a later operational outcome.
Included channelsPaid search placements and permission-based email to opted-in contacts.
Deferred workOrganic social publishing and SEO expansion are Deferred work for this six-week horizon.
Excluded channelsInfluencer partnerships, new social channels, and new automation flows are excluded.
HandoffsPaid search placement or permission-based email → shared trial landing page → qualified trial request → consented email follow-up.
Shared assetsApproved creative master with the core offer message and visual treatment; one shared trial landing page used by both included channels.
Strategic assumptionsOffer terms remain consistent. Email and follow-up use consented contacts only. Both included channels use the shared destination.

2. Separate commitments from planning assumptions

From commitments to operating constraints

A fixed FocusFlow strategy with paid search and permission-based email flowing to one landing page, then feeding a separate six-week execution board with people, cash, and capacity constraints.

The strategic core is carried forward; operating figures are Planning assumptions for execution.

Add operating assumptions, not strategic changes

Record these new Planning assumption inputs without using them to redesign FocusFlow:

  • Horizon: Week 1 through Week 6
  • Weekly allocations before reserve: Marketing Lead 10 h/week; Content/Design 15 h/week; Web/Analytics 10 h/week; Approver 5 h/week
  • A 20% reserve leaves planned weekly limits of 8 h, 12 h, 8 h, and 4 h, respectively
  • Cash ceiling: $3,000 for Base; $1,800 for Constrained
  • In Constrained, Content/Design has 10 h/week before reserve and 8 h/week after reserve; other roles remain unchanged
  • Operations ceiling: 20 new-customer starts/week

These fictional figures will later test capacity, cash, and forecast feasibility. They are not spending instructions and do not change the carried-forward channel portfolio.

Example

Set up the reusable artifact

Your artifact can now have this compact start:

FocusFlow roadmap

Continuity brief
Carried forward: [the populated FocusFlow facts above]
Planning assumption: six-week horizon, role allocations, reserve, cash ceilings, and operations ceiling.

Roadmap
[Add bounded work packages here]

Resource budget
[Complete later]

Scenarios and assumptions
[Complete later]

Later steps will sequence, assign, cost, and compare this same roadmap.

3. Turn activity labels into bounded deliverables

Define work that can be completed

A work package is a bounded deliverable that can be completed, checked, and handed off. A label such as “do social media” or “improve paid search” is not a package: it has no finish line and may introduce unsupported work.

For every proposed package, state:

  1. Deliverable — what will exist.
  2. Observable completion condition — how someone can verify it is finished.
  3. Trace — the carried-forward objective, handoff, Shared asset, or necessary readiness requirement it serves.

At this stage, define the work. Detailed dependency order, Readiness gates, ownership, workload, cash, and forecasts follow in later steps.

Turn broad activities into traceable packages

These packages stay inside FocusFlow’s stated channel scope and use its shared destination rather than creating a new tactic.

A finishable output and a backward trace make a package eligible for the Roadmap.
Too vagueBounded work packageObservable completion conditionTrace
Create contentFinalize the approved creative master for paid search and permission-based email.The reusable master is accepted and available once for both channel uses.Shared asset and consistent offer.
Run paid searchPrepare the paid-search placement set using the approved creative master and shared landing-page URL.Placement copy and destination link are complete and ready for required checks.Included channel and paid-search-to-destination handoff.
Send emailBuild the permission-based email for opted-in contacts using the shared offer and destination.Email copy, destination link, and consented audience selection are complete.Included channel and email-to-destination handoff.
Improve conversionPrepare the shared trial landing-page launch package.The page presents the carried-forward offer and supports a qualified trial request.Objective, shared destination, and both channel handoffs.

4. Practice: recognize executable work

Identify executable work

Which proposal is ready to enter the FocusFlow roadmap as a work package?

5. Apply: distinguish and trace two packages

Build the first traceable roadmap entries

For the FocusFlow case, assess these four proposed entries:

A. Be more active on social media.
B. Finalize the reusable creative master for paid search and permission-based email; it is complete when one approved master is available for both uses.
C. Improve paid-search results.
D. Build the permission-based email for opted-in contacts; it is complete when its copy, shared destination link, and consented audience selection are complete.

Identify the two bounded work packages. For each selected package, write its deliverable, completion condition, and a trace to a named FocusFlow objective, handoff, Shared asset, or necessary readiness requirement. Finish with one sentence explaining why the other statements cannot be scheduled as written.

Write at least 180 characters (0/180).

Step 2 of 8

Sequence Dependencies and Readiness Gates

Sequence FocusFlow work through Prepare, Activate, and Optimize so shared assets, approvals, consent requirements, and measurement checks are ready before dependent activity launches.

Carry forward the pathway

Start with continuity, not a new strategy

Continuity brief

Carried forward: FocusFlow’s existing audience, offer, objective and outcome definition; its included, deferred, and excluded channels; the channel handoffs; shared assets; and strategic assumptions. Keep these decisions intact—this roadmap sequences their execution rather than reopening strategy.

The carried-forward pathway is: included discovery activity → shared destination → permitted follow-up. A shared destination and consistent offer are reusable upstream assets, not separate production jobs for each channel.

Planning assumption: map work across Week 1 through Week 6 using the phases Prepare, Activate, and Optimize. A phase changes only when its required conditions are ready; a calendar week is not proof of readiness.

A shared asset sits upstream

A dependency map shows one shared destination and offer feeding discovery and follow-up activities through a readiness checkpoint.

Prepare reusable inputs first. Downstream activity activates only after the readiness checkpoint is passed.

Make the phase transition conditional

Write conditional roadmap rows

Add a short dependency sequence to the Roadmap section of your FocusFlow roadmap. Use the required headers now; detailed ownership and effort estimates are added later.

Roadmap
Phase/week | Work package | Accountable owner | Contributors/approver | Effort by role | Dependency/gate | Handoff
Prepare / Week 1 | Produce shared destination and offer asset | To assign | Required Approver | Add later | Matches Continuity brief | Asset enters preflight
Prepare / Week 1 | Complete consent and measurement preflight | To assign | Required contributors | Add later | Usable destination | Result to Readiness gate
Prepare / Week 2 | Confirm Readiness gate | To assign | Approver | Add later | All conditions confirmed | Go/no-go to activation
Activate / Week 2–6, only when ready | Run included activity and carried-forward handoff | To assign | Required contributors | Add later | Readiness gate passed | Discovery to destination to follow-up
Optimize / after activation | Refine the live pathway | To assign | Required contributors | Add later | Activity has activated | Updated work enters roadmap

“Week 2–6” reserves possible timing; it does not authorize a launch. Work in Prepare may run in parallel only when it does not need an unfinished input.

Observable readiness conditions

Use this gate before moving from Prepare to Activate. Record a visible confirmation rather than treating a scheduled date as confirmation.

All applicable conditions must be met for the Readiness gate to pass.
Gate conditionObservable confirmationIf unmet
Usable destinationThe destination can support the carried-forward next action.Keep activation blocked.
Consistent offerThe shared asset and destination present the same offer terms.Correct the inconsistency.
Required approvalThe Approver has recorded approval.Wait for approval or revise.
Consent requirementCollection and follow-up follow the carried-forward consent plan.Resolve the requirement.
Measurement preflightA test confirms the expected measurement path.Fix and recheck before activation.

Practice: permit only safe parallel work

Check the dependency logic

The shared asset is awaiting required approval. The destination work can begin, and the consent and measurement preflight can be prepared. Which pair can run in parallel now?

Apply the readiness gate

Build the dependency sequence

For FocusFlow, place these packages into ordered layers. Identify the package(s) that can run in parallel, then explain why activation is blocked when required approval has not been recorded.

Packages:

  • Draft the shared offer and usable destination
  • Prepare the consent and measurement-preflight checklist
  • Obtain required approval
  • Complete the consent and measurement preflight
  • Activate the included discovery activity and its carried-forward handoff
  • Optimize the live pathway

Use a format such as “Layer 1,” “Layer 2,” and so on. State the unmet Readiness gate condition explicitly.

Write at least 180 characters (0/180).

Step 3 of 8

Make Ownership and Review Work Visible

Assign clear ownership, visible review work, role-level effort, and actionable handoffs to FocusFlow roadmap packages.

Separate ownership from contribution

One owner, several roles

Carried forward — FocusFlow: keep the existing audience and offer, objective and outcome definition, included/deferred/excluded channels, channel handoffs, shared assets, and strategic assumptions from the Continuity brief. This roadmap does not reopen those choices; it makes execution accountable.

For every work package, name exactly one Accountable owner. That person is answerable for completion and for making the next handoff happen. They may delegate tasks, but accountability stays visible. List people who help separately as contributors, and list a required Approver separately from both.

Make responsibilities distinct

A work package has one emphasized accountable owner, separate contributors and approver, and an arrow showing a downstream handoff.

Separate accountability, contribution, approval, and handoff so that a finished task can move reliably to the next activity.

Estimate effort by role

Put the work inside the roadmap row

Planning assumption: estimate effort by role, rather than using one undifferentiated total. Include preparation, production, checking, expected revision, and approval. This makes work that is often treated as “extra” visible before activation.

The row below uses an already selected FocusFlow destination and handoff. It does not add a new channel or change the carried-forward strategy.

Worked responsibility-and-effort record

markdown
Phase/week | Work package | Accountable owner | Contributors/approver | Effort by role | Dependency/gate | Handoff
Prepare / Week 1 | Landing-page launch package | Web/Analytics | Marketing Lead; Content/Design; Approver | Marketing Lead: 1 h (brief/check); Content/Design: 3 h (draft/revision); Web/Analytics: 3 h (build/test); Approver: 0.5 h (review) | Approved offer; consent requirements; measurement-preflight criteria | Accepted page URL and validated event check to Marketing Lead for activation

Example

Read the record

Web/Analytics is accountable for the package, even though several roles work on it. The Content/Design estimate already includes revision after review. The Approver’s 0.5 h is planned hands-on review work, not an invisible addition after production is “finished.”

Plan approval and handoff timing

Make the handoff schedulable

A handoff is usable only when it names all three parts: the deliverable, an acceptance condition, and the receiving person or role. “Send page to marketing” is not enough; the receiver needs to know what is accepted and ready to use.

Also record hands-on review effort separately from elapsed turnaround. An approver may spend little time reviewing but return a decision days later. Activation must wait for the decision and any planned revision, even while the reviewer’s effort total remains small.

Review timing versus work effort

For the same FocusFlow launch package, record both timing measures and the accepted downstream input.

Hands-on work and elapsed waiting time affect the roadmap differently.
RecordMeaningFocusFlow entry
Review effortHands-on time used by the reviewer0.5 h
Elapsed turnaroundTime until a review decision returns2 working days
HandoffAccepted input and receiving roleAccepted page URL + validated event check to Marketing Lead

Review can delay a ready package

A workflow timeline shows brief review effort, a two-day decision wait, a possible revision loop, and then a handoff to activation.

A short review effort can have a longer turnaround. Plan both the review work and the waiting period before the downstream handoff.

Practice: complete the responsibility record

Complete the execution record

Complete the responsibility-and-effort record for the same launch package.

markdown
Accountable owner: 
Contributors: 
Required approval by: 
Review effort: 
Elapsed turnaround: 
Handoff: Send the accepted page URL and validated event check to  for activation.

Step 4 of 8

Resolve Weekly Capacity Bottlenecks

Reconcile FocusFlow’s role-week workload against protected capacity, then repair a visible bottleneck while preserving dependencies, readiness, ownership, and handoffs.

Set usable weekly capacity

Capacity is role-specific

Continue the FocusFlow roadmap; capacity planning changes execution feasibility, not the carried-forward strategy. FocusFlow still uses its approved Shared asset and shared trial landing page for paid search placements and permission-based email.

Planning assumption: business-as-usual commitments have already been removed from the weekly allocations. Protect a further 20% reserve for uncertainty, revision, or disruption. Schedule planned work only within the remaining role-specific limit. The reserve is not spare planned capacity and should not be filled with routine work.

Protect a reserve in every role

A role-by-role capacity diagram with protected reserve segments and an overloaded specialist lane.

Capacity belongs to a role and a week. Unused time in one lane does not automatically solve a bottleneck in another.

Weekly planning limits

Apply the reserve before assigning roadmap work.

FocusFlow allocations after business-as-usual commitments.
RoleWeekly allocation20% reservePlanned weekly limit
Marketing Lead10 h/week2 h8 h
Content/Design15 h/week3 h12 h
Web/Analytics10 h/week2 h8 h
Approver5 h/week1 h4 h

Locate the bottleneck

Check the grid, not just the total

A six-week total can look feasible while a single week is impossible. Check every role-week cell: add the effort assigned to that role in that week, then compare it with that role’s planned weekly limit.

In this illustration, Content/Design has 48 h across six weeks, below its 72 h of planned six-week capacity. Yet its Week 2 concentration creates an overload. Concurrent Shared asset revisions, activation work, or reviews can cause this pattern.

Spare time for Web/Analytics does not resolve a Content/Design bottleneck. Reassignment is valid only when a qualified contributor is explicitly named and the ownership, review, dependency, and Handoff still make sense.

Illustrative role-week load

Each cell is planned hands-on effort for that role in that week.

The whole-period total conceals a concentrated Content/Design bottleneck.
WeekMarketing LeadContent/DesignWeb/AnalyticsApprover
Week 16 h11 h7 h2 h
Week 27 h14 h8 h4 h
Week 38 h9 h6 h2 h
Week 45 h6 h7 h3 h
Week 54 h5 h4 h2 h
Week 63 h3 h3 h1 h

Record a feasible correction

Repair without breaking the pathway

Repair overload openly rather than hiding it in the reserve. You may reduce optional scope, shift work to a feasible week, explicitly reassign work to a qualified contributor, or mark it as Deferred work.

Protect prerequisites first: the usable shared destination, approved Shared asset, consent requirement, measurement preflight, and required approval. A repair must retain one Accountable owner, its Dependency/gate, and a usable Handoff. Record the schedule consequence: if a variant moves, its dependent update moves too; it is not available on the original date.

Example

Worked correction in the FocusFlow roadmap

In the illustrative grid, Week 2 has 14 h of Content/Design work: 8 h for paid-search creative adaptation, 4 h for the core permission-based email, and 2 h for an optional email visual variant.

Keep the required paid-search and core-email packages conditional on the Readiness gate. Move only the optional variant to Week 3 as Deferred work:

Optimize / Week 3 | Deferred work: optional email visual variant | Marketing Lead | Content/Design | Content/Design: 2 h | Core email accepted | Variant to Marketing Lead; optional update moves to Week 3

Week 2 Content/Design effort becomes 12 h; Week 3 rises from 9 h to 11 h. The core email can still activate when the gate passes, while the optional variant has an explicit later Handoff.

Warning

Keep the gate valid

Do not solve an overload by consuming the reserve in advance, silently moving effort to another role, or activating before the Readiness gate. These actions conceal risk instead of making the roadmap feasible.

Apply the capacity check

Capacity-repair data

Use the two tables together for this capacity-check excerpt. All figures are internal staff effort; do not introduce cash changes.

The Week 2 activation rows are conditional: they can proceed only if the Week 1 handoff is accepted and the Readiness gate has passed. No role effort exists beyond the rows shown. Keep the same Accountable owner and Handoff when you repair the schedule.

Work packages and effort

These rows contain all planned hands-on effort by role.

FocusFlow capacity-check excerpt, scheduled work.
PackagePhase/weekWork packageAccountable ownerContributors/approverEffort by role
R1Prepare / Week 1Shared destination, creative master, and preflightWeb/AnalyticsContent/Design; Marketing Lead; ApproverMarketing Lead: 5 h; Content/Design: 7 h; Web/Analytics: 7 h; Approver: 3 h
R2Activate / Week 2Paid-search placement activation packageMarketing LeadContent/Design; Web/Analytics; ApproverMarketing Lead: 3 h; Content/Design: 8 h; Web/Analytics: 2 h; Approver: 1 h
R3Activate / Week 2Permission-based core emailMarketing LeadContent/Design; Web/Analytics; ApproverMarketing Lead: 3 h; Content/Design: 3 h; Web/Analytics: 4 h; Approver: 2 h
R4Activate / Week 2Optional email visual variantMarketing LeadContent/DesignContent/Design: 2 h
R5Optimize / Week 3Planned live-pathway refinementWeb/AnalyticsMarketing Lead; Content/Design; ApproverMarketing Lead: 4 h; Content/Design: 4 h; Web/Analytics: 5 h; Approver: 2 h

Dependencies and handoffs

Use these gates and Handovers when deciding what can move.

Each package retains its dependency and receiving role.
PackageDependency/gateHandoff
R1Consistent offer; consent and measurement checks; required approvalAccepted master, usable landing-page URL, and passed preflight to Marketing Lead for activation
R2Readiness gate passed; approved Shared assetAccepted placement set to Marketing Lead for activation using the shared landing page
R3Readiness gate passed; consented audience; approved Shared assetApproved email and shared landing-page URL to Marketing Lead
R4Readiness gate passed; approved Shared assetOptional variant to Marketing Lead after acceptance
R5Included activity is liveChecked refinement to Marketing Lead

Make a defensible correction

Reconcile the weekly schedule

Reconcile and repair the capacity-check excerpt from the preceding screen.

  1. Calculate the planned weekly limit after reserve for all four roles.
  2. Sum the listed Week 2 rows by role. Identify the overloaded role-week and its excess; do not rely on a six-week total.
  3. Make one feasible schedule revision. State the changed work package, its new timing or reduced scope, and the downstream schedule consequence. Retain the Accountable owner, the accepted Week 1 handoff, and the Readiness gate. Show that the affected role fits its limit in the revised week.

Write at least 220 characters (0/220).

Step 5 of 8

Build a Cash-and-Time Resource Budget

Build the Resource budget section of the FocusFlow roadmap by keeping cash categories, timing, shared assets, and internal staff time visible and reconcilable.

Separate cash from staff time

Two resources, two views

Carried forward: FocusFlow’s audience, offer, objective, outcome definition, channel decisions, handoffs, and shared assets remain unchanged. This step adds the Resource budget section to the FocusFlow roadmap; it does not reopen strategy.

Use two linked views:

  • A cash ledger records only cash in Advertising, External production, and Tools.
  • A Staff time view records internal role hours from the Roadmap.

Internal work can cost $0 in the cash ledger and still be scarce. Reconcile every staff-time line to its roadmap work package and its role-level effort estimate. For Base, all cash lines together must stay at or below the six-week ceiling of $3,000.

Keep cash and time separate

A diagram shows a roadmap feeding separate cash and staff-time ledgers, with one shared asset serving two channels from a single entry.

Cash and staff hours are connected to the same roadmap, but they are not interchangeable resources.

Tip

Do not convert one buffer into another

Record timing and charging pattern, not just a six-week total. For example, mark a tool as recurring and an external creative fee as one-off.

Uncommitted cash is money not assigned to a ledger line. It is not permission to add work without checking owners and dependencies. Likewise, the 20% staff-time reserve is a buffer already withheld from planned weekly limits; it is not spare planned capacity.

Reconcile a plan-wide ledger

Example

Worked FocusFlow ledger

This illustrative Base ledger uses only work already represented in the roadmap. A reusable asset has one production entry even though several carried-forward channels use it. Replace the channel references with the ones in your own Continuity brief; do not create separate production charges for the same approved asset.

Cash view

Cash ledger for the six-week Base plan

The total cash commitment is $2,380, leaving $620 uncommitted under the $3,000 Base ceiling.
TimingEntryCash categoryCashCharge pattern
Week 1Shared asset: approved creative master; used by the two carried-forward included channelsExternal production$600One-off
Week 1–Week 6Analytics connectorTools$30/week = $180Recurring
Week 3–Week 6Approved paid placementsAdvertising$400/week = $1,600Flight

Staff-time view

Staff-time view reconciled to Roadmap work packages

These 15 h remain hours. They are checked against the matching roadmap entries and role-week limits, not added to the $2,380 cash total.
Roadmap work packageRoleStaff timeLedger check
Create shared assetContent/Design6 hMatches production work
Measurement preflightWeb/Analytics3 hMatches readiness work
Approval reviewApprover2 hMatches approval work
Placement setupMarketing Lead4 hMatches activation setup

Practice: classify resource entries

Classify the entries

Match each resource entry to its correct budget category.

Tap an item and then its matching pair.

Apply the full resource check

Audit a duplicated shared cost

Audit this six-week Base draft. Write a four-part ledger check.

A. Week 3–Week 6: $300/week for approved paid placements.
B. Week 1: $500 contractor invoice to create one reusable visual kit.
C. Week 4: $500 contractor invoice recorded again for that same visual kit; there is no new deliverable.
D. Week 1: $120 analytics connector charge for six weeks.

Roadmap staff time: Content/Design 6 h; Marketing Lead 3 h; Web/Analytics 4 h; Approver 2 h.

  1. Classify A–D using the resource-budget labels.
  2. State which duplicated shared-asset charge to remove.
  3. Give the corrected cash total for each cash category and the overall cash total.
  4. Give the staff-time total and explain how it belongs in the ledger.

Write at least 120 characters (0/120).

Step 6 of 8

Make Forecasts Respect Time and Business Capacity

Document a conditional FocusFlow forecast that respects readiness, channel timing, conversion lag, and the capacity to serve new customers.

Start with the journey and activation conditions

Forecast from the carried-forward journey

Use the existing FocusFlow roadmap as the source of truth. Its audience, offer, objective, selected and deferred channels, handoffs, shared assets, and strategic assumptions are Carried forward; do not reopen those decisions here.

A forecast adds operating logic to that plan. Preserve the exact primary-conversion outcome name from the integrated plan, then map it through the journey:

selected touchpoint → agreed destination → primary conversion → new-customer start

A primary conversion signals potential demand. A new-customer start is the operational outcome that must fit delivery capacity. They are not automatically the same count.

Forecast only the period in which activity can actually run. Prepare work, approvals, the usable destination, consent requirements, and measurement preflight must pass their Readiness gate before Activate work begins.

Timing changes what can be forecast

A six-week flow shows preparation and a readiness gate before channel activation, then primary conversions flowing to new-customer starts limited by operations capacity.

Do not assign mature channel results to Weeks 1–2 when the work is still in Prepare. A conversion can also become a start only after its conversion lag.

Create a conditional assumption register

Classify inputs before using them

Build the assumption register before calculating a range. Every input needs a source status. Evidence is supported by the carried-forward plan or verified records. A Planning assumption is an explicit, revisable operating figure. An Unknown is not silently converted into a precise forecast number.

Forecast register

Illustrative FocusFlow forecast register

The operational ceiling applies to new-customer starts, not to upstream traffic or primary conversions.
Forecast inputStatusHow it constrains the forecast
Carried-forward journey and named primary conversionEvidenceDefines the conversion path
Readiness gate clears by end of Week 2Planning assumptionActivation cannot begin earlier
Channel activation after the gatePlanning assumptionWeeks 1–2 have no active-channel result
Primary conversion to start rate: 50%–60%Planning assumptionMaps demand to potential starts
Conversion-to-start lag: 1 weekPlanning assumptionMoves starts into a later week
Operations ceiling: 20 new-customer starts/weekPlanning assumptionCaps supported starts
Organic contribution during this horizonUnknownDo not add a precise volume yet
Effect of extra cash on resultsUnknownDo not assume proportional returns

Apply lag before applying the operations ceiling

Example

Worked six-week forecast

This illustration assumes the Readiness gate clears at the end of Week 2. Week 3 is a ramp period with 8–12 primary conversions. Weeks 4–6 have a conditional range of 16–24 primary conversions per week. The 50%–60% mapping and one-week lag determine when potential starts appear.

The Week 6 primary conversions may create starts in Week 7, outside this roadmap horizon. They should not be counted as completed Week 6 starts.

Timing and capacity view

Potential starts are calculated before applying the operational limit.

Ranges are conditional on the stated assumptions; they are not promises of performance.
WeekPrimary conversionsPotential startsSupported starts
Week 10; Prepare work00
Week 20; gate not cleared00
Week 38–12; ramp0; 1-week lag0
Week 416–244–7; from Week 34–7
Week 516–248–14; from Week 48–14
Week 616–248–14; from Week 58–14

Revise conditions, not reality

Capacity becomes binding only when potential starts exceed 20 in a week. For example, if a revised, supported input projects 40 primary conversions in Week 4, Week 5 potential starts are 20–24. Operations can support no more than 20. The remaining 0–4 are potential demand, not completed starts; record a handling assumption such as delayed onboarding or a waitlist.

An extra budget line does not prove that this higher input will occur. Its effect remains Unknown until supported by appropriate evidence.

Correct an unsupported full-period forecast

Correct the forecast

A draft says: “FocusFlow will produce 40 primary conversions in every week from Week 1 through Week 6. All 40 become new-customer starts in the same week. Adding $300 will raise results proportionally.”

Correct this draft in three short bullets. Use these proposed inputs: 12 primary conversions in Week 3, 40 in Week 4, a 50%–60% conversion-to-start mapping, a one-week lag, and a ceiling of 20 new-customer starts/week.

  1. Correct the timing and show the resulting potential starts for Weeks 4 and 5.
  2. Identify which asserted inputs or claims are Unknown without evidence, versus Planning assumptions.
  3. State the supported Week 5 starts and how any excess demand must be handled.

Write at least 180 characters (0/180).

Step 7 of 8

Compare Feasible Scenarios and Trade-offs

Create a feasible constrained-resource scenario and justify what changes, what remains protected, and what is deferred.

Fix the scenario inputs

Keep the strategic core fixed

Continue the same FocusFlow roadmap. A scenario changes operating feasibility, not the strategic core.

Carried forward: FocusFlow serves operations leads at small client-service teams with a 14-day guided trial and setup consultation. Its objective is qualified trial requests. Included channels are paid search placements and permission-based email to opted-in contacts. Both use the approved Shared asset and shared trial landing page, leading to a qualified trial request and consented email follow-up. Organic social publishing and SEO expansion remain Deferred work.

Protect the work that makes this pathway viable: the Shared asset, usable destination, consent safeguards, measurement preflight, required approval, and the Readiness gate. Then make targeted decisions: protect, reduce, defer, or replace. Do not cut every package by the same percentage. A replacement is not free: assess its cash, staff time, quality, dependencies, acceptance condition, and Handoff before scheduling it.

Same plan, different feasible execution

Side-by-side Base and Constrained roadmaps retain the same readiness foundations while the constrained roadmap reduces optional scope and moves optional work outside the six-week horizon.

Change scope and timing deliberately; do not remove the foundations that make the carried-forward handoffs usable.

Scenario frame

Record the operating inputs before changing a work package. All role limits below are after the protected 20% reserve.

Base and Constrained share the same strategic core, Readiness gate, and operations limit.
Planning dimensionBaseConstrained
Six-week cash ceiling$3,000$1,800
Marketing Lead limit8 h/week8 h/week
Content/Design limit12 h/week8 h/week
Web/Analytics limit8 h/week8 h/week
Approver limit4 h/week4 h/week
Activation ruleConditional on the Readiness gateSame conditional Readiness gate
Operations ceiling20 new-customer starts/week20 new-customer starts/week

Tip

Keep cash and capacity separate

A cash ceiling is a maximum, not a spending target. Record any remainder as uncommitted cash, but do not treat it as extra Content/Design capacity or as permission to consume the staff-time reserve. Cash, role capacity, approval availability, and dependencies are separate constraints.

Inspect the data behind the trade-off

Make revised workload calculable

Use the package blocks and fixed background load together. The blocks show every role’s hands-on effort for work whose timing or scope changes. “Prepare” work may be completed before the gate, but launch remains blocked until the Readiness gate is confirmed. P4’s reduction is specific: two paid-search copy variants become one accepted core placement set using the approved Shared asset and shared landing-page URL.

Moved package blocks

For P4 and P5, the preparation and launch effort are separate parts of the same package. A zero means that role has no hands-on effort in that package.

Use these blocks when adding revised role-week totals.
PackageBase timingConstrained timingEffort by roleDependency/gate and Handoff
P1 Shared assetWeek 1Week 1Marketing Lead: 1 h; Content/Design: 6 h; Web/Analytics: 3 h; Approver: 1 hRequired approval; accepted master to P4 and P5
P2 Destination, consent, and preflightWeek 1Week 2Marketing Lead: 1 h; Content/Design: 3 h; Web/Analytics: 3 h; Approver: 1 hUsable destination; passed preflight to P3
P3 Confirm Readiness gateEnd of Week 2End of Week 2Marketing Lead: 1 h; Content/Design: 0 h; Web/Analytics: 1 h; Approver: 1 hP1 and P2 accepted; recorded go/no-go to P4 and P5
P4 Paid-search placement setPrepare Week 2; launch Week 3Prepare Week 3; launch Week 4Base preparation: Marketing Lead 2 h, Content/Design 6 h, Web/Analytics 1 h, Approver 1 h; Constrained preparation: Marketing Lead 2 h, Content/Design 4 h, Web/Analytics 1 h, Approver 1 h; launch: Marketing Lead 1 h, Web/Analytics 1 hApproved master and URL; accepted set to Marketing Lead
P5 Core permission-based emailPrepare Week 2; launch Week 3Prepare Week 3; launch Week 4Preparation: Marketing Lead 2 h, Content/Design 4 h, Web/Analytics 1 h, Approver 1 h; launch: Marketing Lead 1 h, Web/Analytics 1 hConsented audience, master, URL, and gate; accepted email to Marketing Lead
P6 Optional email visual variantWeek 4Beyond Week 6: Deferred workMarketing Lead: 1 h; Content/Design: 2 h; Web/Analytics: 0 h; Approver: 0 hCore email live; optional variant to Marketing Lead after acceptance

Fixed background load

These are all other unchanged roadmap loads. They exclude P2–P6, include P1 in Week 1, and must be added to the moved package blocks. They make each revised role-week total fully checkable.

Hours by role after reserve; every fixed row is already within its role limit.
WeekMarketing LeadContent/DesignWeb/AnalyticsApprover
Week 11 h6 h3 h1 h
Week 22 h0 h1 h0 h
Week 31 h0 h2 h0 h
Week 43 h2 h3 h1 h
Week 53 h2 h3 h1 h
Week 63 h1 h2 h1 h

Cash and forecast comparison inputs

Base uses the Shared asset once for both included channels. Its gate clears at the end of Week 2, so activation begins in Week 3. In Constrained, activation moves to Week 4 and the paid flight is reduced; Base primary-conversion ranges must not be copied as if results decline proportionally.

Forecast ranges remain conditional on recorded assumptions and channel lead time.
AreaBaseConstrained
External productionShared asset for both included channels: $600Shared asset for both included channels: $600
ToolsAnalytics connector: $30/week × 6 = $180Analytics connector: $30/week × 6 = $180
Advertising$400/week, Week 3–Week 6 = $1,600$300/week, Week 4–Week 6 = $900
Cash total$2,380; $620 uncommitted$1,680; $120 uncommitted
Activation timingWeek 3, after end-of-Week-2 gateWeek 4, after preparation in Week 3
Primary conversionsWeek 3: 8–12; Week 4–Week 6: 16–24/weekDo not reuse Base volumes; a new range is a Planning assumption or Unknown
Start mapping50%–60%; 1-week lagSame mapping unless explicitly revised
Operational consequenceSupported starts cannot exceed 20/weekSame 20 new-customer starts/week ceiling

Carry the consequences into the scenario

Verify the Constrained schedule

This feasible Constrained revision protects P1, P2, and P3; reduces P4 to one accepted core placement set; keeps the core consented email; and marks P6 as Deferred work beyond Week 6. It does not replace a carried-forward channel. P2 moves to Week 2, P3 remains at the end of Week 2, preparation moves to Week 3, and activation moves to Week 4. The totals below include both the fixed background load and every moved package block.

Complete Constrained role-week totals

Compare every cell with its limit: Marketing Lead 8 h/week, Content/Design 8 h/week, Web/Analytics 8 h/week, and Approver 4 h/week.

All totals fit the Constrained role limits after reserve.
WeekMarketing LeadContent/DesignWeb/AnalyticsApprover
Week 11 h6 h3 h1 h
Week 24 h3 h5 h2 h
Week 35 h8 h4 h2 h
Week 45 h2 h5 h1 h
Week 53 h2 h3 h1 h
Week 63 h1 h2 h1 h

Test an approval-delay contingency

Contingency: required approval is returned and recorded at the end of Week 3 rather than the end of Week 2. P2 remains complete in Week 2. P3 moves to the end of Week 3, while P4 and P5 can be prepared and held in Week 3 because their launch still depends on P3. Their launch shifts to Week 5. P6 remains Deferred work.

Marketing Lead owns P3, P4, and P5; Web/Analytics contributes to all three; the Approver supplies P3’s recorded decision. Advertising now runs only in Week 5–Week 6: $600. Cash becomes $1,380, leaving $420 uncommitted. The earliest primary-conversion ramp shifts to Week 5 and, with the 1-week lag, the earliest potential starts shift to Week 6. Do not assert a new conversion volume without an explicit Planning assumption or Evidence.

Approval-delay role-week totals

These totals include the moved P3 gate effort, held preparation in Week 3, shifted launch in Week 5, and all fixed background load.

The approval delay changes timing but remains capacity-feasible; launch stays conditional on the recorded gate.
WeekMarketing LeadContent/DesignWeb/AnalyticsApprover
Week 11 h6 h3 h1 h
Week 23 h3 h4 h1 h
Week 36 h8 h5 h3 h
Week 43 h2 h3 h1 h
Week 55 h2 h5 h1 h
Week 63 h1 h2 h1 h

Apply the comparison and contingency

Build and justify the feasible scenario

Create a compact update for the Scenarios and assumptions section of your FocusFlow roadmap. Use the supplied package blocks, fixed background load, and scenario totals from the preceding screens.

First, revise Base into Constrained: show Advertising, External production, and Tools; the total cash and uncommitted cash; Staff time separately; the protected work; P4’s reduced deliverable; P6 as Deferred work; and the Week 4 activation consequence. Verify the preserved Readiness gate, relevant Handoffs, role-week limits, and conditional forecast effect.

Then choose one contingency:

A. Approval delay. Use the supplied approval-delay totals. State which owners and gate work are affected, why P4 and P5 launch in Week 5 rather than Week 4, the revised advertising cash, the explicit Deferred work, and the Week 6 earliest-start consequence.

B. Forecast revision. Assume the conversion-to-start Planning assumption changes to 40%–50%, while the 1-week lag remains. Using Base primary conversions of 8–12 in Week 3 and 16–24 in Week 4, calculate the potential-start ranges for Weeks 4 and 5. State whether the 20 new-customer starts/week ceiling binds and label the revised mapping correctly.

Keep the analysis conditional. Do not create performance-detection thresholds or decision rules; those belong to the next tutorial.

Write at least 700 characters (0/700).

Step 8 of 8

Finalize and Check Your Marketing Roadmap

Assemble, audit, and preserve a feasible FocusFlow roadmap for the next stage of the integrated marketing-plan capstone.

Build the final roadmap

Assemble one reusable artifact

Your completed artifact is the FocusFlow roadmap: a reusable, plain-text extension of the same integrated plan. Do not reopen the strategy or add unsupported channels. Carry forward the existing audience, offer, objective, included/deferred/excluded channels, handoffs, shared assets, and strategic assumptions.

Assemble your work in four compact sections:

  1. Continuity brief — the carried-forward strategic core and the execution assumptions.
  2. Roadmap — the phased work packages using the required roadmap headers.
  3. Resource budget — cash ledger plus separate staff-time view.
  4. Scenarios and assumptions — Base and Constrained comparison, forecast register, operations limit, and rationale.

Keep tables compact. A section can use more than one small table; do not force the full plan into one oversized table.

A four-part roadmap artifact in which continuity information connects to work sequencing, resources, and scenario assumptions.

The four sections should connect: strategic continuity informs execution, resources constrain it, and scenarios make changed assumptions visible.

Example

Plain-text structure

Use this outline, then replace the bracketed prompts with your completed work from earlier steps:

FocusFlow roadmap

Continuity brief
[Carried forward: audience, offer, objective/outcome, channel decisions,
handoffs, shared assets, strategic assumptions]
[Planning assumption: six-week horizon, role allocations, reserve, operations ceiling]

Roadmap
Phase/week | Work package | Accountable owner | Contributors/approver | Effort by role | Dependency/gate | Handoff
[Your rows for Week 1 through Week 6]

Resource budget
[Cash ledger: Advertising, External production, Tools]
[Staff time by role and week; shared assets counted once]

Scenarios and assumptions
[Base versus Constrained comparison]
[Forecast register: Evidence, Planning assumption, Unknown]
[Protected priority, binding constraint, trade-off, Deferred work]

Audit feasibility

Audit before you call it complete

Run a final feasibility audit after assembly. This is a consistency check, not a new planning method. Correct the roadmap wherever a check exposes a contradiction or an unrecorded consequence.

Final feasibility audit

Check the finished artifact from top to bottom.

Every “no” requires a visible correction in the relevant roadmap section.
Audit areaQuestion to answer
TraceabilityDoes each work package serve a carried-forward objective, handoff, shared asset, or readiness requirement?
DependenciesDo required asset, consent, approval, and measurement-preflight work occur before dependent activation?
Readiness gateIs Activate conditional on observable readiness rather than merely a planned date?
OwnershipDoes every work package have one Accountable owner, named contributors, and an Approver where required?
CapacityDoes each role stay within its planned weekly limit: Marketing Lead 8 h, Content/Design 12 h, Web/Analytics 8 h, Approver 4 h?
CashDo Base cash lines total no more than $3,000, with no duplicated Shared asset cost?
ConstrainedDoes Constrained cash total no more than $1,800 and Content/Design stay within 8 h/week?
ForecastDo timing, lead times, conversion dependencies, and the 20 new-customer starts/week operations ceiling bound the forecast?

Tip

Common final check

Do not treat unused cash as extra staff capacity, or staff-time reserve as uncommitted cash. They are different constraints. Also check that a delayed approval, shared-asset revision, or overloaded specialist has a visible downstream schedule consequence.

State the trade-off and preserve continuity

Make scenario changes visible

The two scenarios must tell a coherent story. Base and Constrained share the strategic core, but Constrained has a lower six-week cash ceiling and less Content/Design capacity. Therefore it must show a concrete change in scope, timing, resource use, expected outcome, or more than one of these.

Protect work that makes the plan viable: essential Shared asset work, required approvals, consent safeguards, and measurement preflight. Then identify what is reduced, deferred, or replaced. A replacement is not free: record its cash, effort, quality, and dependency implications.

Example

Rationale pattern

Write the rationale as a short chain of decisions, not a vague claim that the plan is “optimized.”

Example

Protected priority: [essential asset, safeguard, or gate]
Binding constraint: [cash, named role-week capacity, approval availability, or assumption]
Principal trade-off: [what changes and why]
Deferred work: [specific work package and schedule consequence]

Next-stage handoff: Preserve the roadmap and forecast register so the next tutorial can attach measurement decision rules to this same plan.

Warning

Keep the conclusion conditional

Avoid claiming that a lower budget automatically causes a proportional decline in outcomes. Keep forecasts conditional on the recorded assumptions, activation timing, channel lead time, conversion path, and service capacity.

Complete the capstone handoff

Final application

Complete your FocusFlow roadmap in your own notes or document using the four required headings. Use the audit to revise it before responding.

Then submit a concise four-part completion note. It should confirm that you assembled and checked the artifact, name the most important trade-off, and explain how the preserved roadmap supports the next stage of this same capstone.

Submit your completion note

Write four labeled lines:

  1. Audit result: the most important correction or confirmation from your feasibility check.
  2. Protected priority: the work you kept and why.
  3. Trade-off and Deferred work: the binding constraint, the change made, and its schedule consequence.
  4. Next-stage handoff: how your roadmap and assumption register will support the next tutorial's measurement decision framework.

Use details from your own completed FocusFlow roadmap; do not introduce a new strategy, channel, or decision rule.

Write at least 280 characters (0/280).

Download the App now to have access to + 5000 free courses, exercises, certificates and lots of content without paying anything!

  • 100% free online courses from start to finish

    Thousands of online courses in video, ebooks and audiobooks.

  • More than 60 thousand free exercises

    To test your knowledge during online courses

  • Valid free Digital Certificate with QR Code

    Generated directly from your cell phone's photo gallery and sent to your email

Cursa app on the ebook screen, the video course screen and the course exercises screen, plus the course completion certificate