The Growth Prioritisation Framework

Most growth prioritisation fails because it ranks ideas instead of sequencing commercial work. Leadership workshops produce long lists. Everything feels important. Teams leave with enthusiasm and return to inbox priorities by Friday. The growth prioritisation framework exists to kill attractive work that cannot clear a commercial bar, then order what remains by impact, confidence and dependency.

Australian operators between two and twenty million dollars in revenue feel this acutely. Marketing wants new channels. Sales wants better leads. Operations wants less chaos. Finance wants proof before spend. Without a shared scoring method, the loudest voice or the latest agency pitch wins. Busy quarters follow. Contribution flatlines.

Prioritisation is not about doing less for its own sake. It is about doing the right work first so compounding returns appear before cash and patience run out. The framework pairs naturally with constraint diagnosis. Constraint names the bottleneck. Prioritisation ranks how to attack it when ten fixes all seem reasonable.

Score every growth initiative on impact, confidence and dependency. Impact estimates contribution or revenue movement if the initiative succeeds within one to two quarters. Use ranges, not false precision. A landing page fix on high-intent traffic might be worth fifteen to thirty qualified enquiries monthly at known close rates. A brand video without distribution logic might be worth zero until defined.

Confidence captures evidence quality. High confidence means recent data, prior tests or strong category patterns support the bet. Medium means plausible but unproven. Low means hope dressed as strategy. Dependency asks what must exist first. Tracking fixes precede channel scale. Qualification rules precede sales hires. Offer clarity precede creative refresh.

Reject or defer initiatives that score high impact but low confidence without a cheap learning plan. Reject initiatives that score high impact but high dependency when prerequisites are not scheduled. An idea that fails all three dimensions should leave the active list entirely, not sit at the bottom to guilt the team.

Start with a brain dump from every function. Marketing channels, CRO tests, CRM fixes, pricing changes, hiring plans, referral programs, website sections, sales scripts, operational throughput improvements. Capture without judging for fifteen minutes, then deduplicate aggressively. Many items are the same fix described differently.

Add constraint context before scoring. Tag each initiative as directly attacking the named constraint, enabling a dependency, or unrelated. Unrelated items default to backlog unless someone articulates a new constraint story with data. This step alone cuts most wish lists by half in typical engagements.

Cap the active list at seven initiatives maximum for a quarter. Include only items with named owners and measurable signals. Everything else sits on a visible backlog with revisit dates. Hidden backlogs reappear as surprise urgent projects and break focus.

Impact estimation terrifies teams without finance training. Use simple commercial arithmetic. Multiply expected volume change by conversion rates and contribution per win. Example: improving qualified rate from forty to forty-five percent on two hundred monthly enquiries with five thousand dollar average contribution and twenty-five percent win rate moves meaningful monthly contribution. Even rough ranges beat abstract high labels.

Compare initiatives with the same numerator. Contribution dollars per quarter beats vanity metrics like impressions or raw leads. When impact is operational, translate to commercial language. Cutting quote turnaround from five days to two may lift win rate three points. Model that lift explicitly.

Document assumptions beside every estimate. Assumptions make revisiting scores easier when reality differs. An initiative projected to add twenty qualified enquiries monthly based on last year's test data carries higher confidence than the same projection based on a vendor slide.

Low-confidence high-impact ideas are not forbidden. They require learning design. Small tests with clear success and failure criteria, capped spend and short timelines. A two-week landing page test on one offer beats a six-month redesign justified by opinion. If the test wins, confidence rises and the initiative moves up. If it loses, you bought information cheaply.

Define kill criteria before launch. Example: if qualified rate does not improve by at least three points in thirty days with two hundred sessions, revert and backlog. Kill criteria protect teams from sunk-cost attachment and protect executives from endless maybe projects.

Confidence rises with closed-loop measurement. Initiatives that cannot be measured belong in research or backlog until measurement exists. Growth prioritisation without measurement discipline is theatre.

Dependencies break roadmaps when ignored. Common dependency chains include tracking before scale, qualification before sales hiring, offer clarity before creative, response routing before ad increase, and capacity planning before geographic expansion. Draw dependencies explicitly for top-ranked initiatives.

Schedule prerequisites as first-class work with owners and dates. A prerequisite is not less important because it is less visible. Fixing form notifications is boring until you realise half your paid search leaks there. Dependency respect separates operators who compound gains from those who repeat the same launch failure quarterly.

When two initiatives depend on each other, merge them into one workstream or redesign scope. Circular dependencies signal muddled thinking. Simplify until sequence is linear.

The framework output is a one-page quarterly roadmap. Name the constraint. List three to five active initiatives in sequence with owners, primary metrics, impact ranges and start dates. Show backlog top five with deferral reasons. Share with agencies and partners so external work aligns.

Sequence vertically, not just by score. Initiative two may score slightly lower than initiative three but must wait for initiative one's output. Roadmaps fail when everything starts on day one. Stagger starts based on capacity and dependency reality.

Include one explicit not doing list. Naming deferred projects reduces hallway relitigation. Operators respect clarity when trade-offs are visible.

Run a weekly fifteen-minute initiative check on active items only. Metric movement, blockers, next action. Run a monthly thirty-minute reprioritisation review. Any initiative without progress in thirty days gets challenged. Pause, re-scope or kill. Run a quarterly full rescoring when constraints may have shifted.

Decisions log in one shared document beats memory. Date, decision, owner, rationale. Future you will forget why TikTok waited. Logs preserve institutional learning and stop repeated debates.

Escalate only blockers that threaten the primary constraint metric. Everything else resolves at working level. Executive attention is a scarce resource. Prioritisation framework protects it for decisions that actually move the scoreboard.

The first mistake is scoring in isolation without the constraint story. Impact labels inflate when every project claims to be strategic. Tie scores to the constraint metric explicitly.

The second mistake is treating all initiatives as equal size. A roadmap of ten large projects is a fantasy. Mix one or two substantial bets with smaller fast signal tests.

The third mistake is ignoring implementation capacity. Your team has finite hours while serving clients. Score feasibility honestly. A perfect initiative with no owner time is backlog fiction.

The fourth mistake is reprioritising weekly because anxiety spiked. Allow tests time to produce signal unless data shows harm. Whiplash destroys agency relationships and internal morale.

The fifth mistake is hiding deferrals. Transparent backlog management builds trust. Silent kills breed politics.

Australian service businesses face rising acquisition costs, mobile-first buyers and seasonal swings. Prioritisation must respect cash flow timing. Initiatives with long payback periods may lose to faster wins when working capital is tight even if long-term impact is larger. Document timing assumptions openly.

Franchise and multi-location operators need local prioritisation inside national themes. A constraint in Brisbane may differ from Perth. Allow regional scoring variants within shared measurement standards.

Agency market churn tempts operators to reprioritise around vendor changes. Run vendor transitions through the same framework. Switching agencies without fixing measurement repeats the cycle. Sometimes the priority is contract clarity, not new creative.

Run prioritisation as a working session, not a month of email opinions. Send participants the initiative list and constraint statement forty-eight hours ahead with instructions to bring impact estimates as ranges. Open the session by reconciling metric definitions for fifteen minutes so scoring uses shared language.

Score impact first in silence on a shared sheet, then discuss outliers. One person anchoring high on pet projects becomes visible quickly when numbers are written before debate. Move to confidence next. Ask what evidence would change the score. Finish with dependency mapping on a whiteboard or shared doc until sequence is linear.

Close with explicit decisions. Three to five active initiatives with owners and start dates. Top five backlog items with deferral reasons. One not-doing item killed entirely if possible. Photograph the board or export the doc the same day. Delay lets hallway negotiations undo the work before lunch.

Budget cuts do not remove the need for prioritisation. They increase it. When media spend drops twenty percent, the framework helps decide which tests pause and which constraint-aligned work continues. Random cuts across all channels usually preserve waste and kill learning bets that were producing signal.

Separate fixed costs from discretionary tests in the initiative list. Retainers, platforms and staff time are harder to cut quickly. Campaign tests and new creative explorations flex faster. Finance and marketing should score flex items together using the same impact and confidence language instead of defaulting to cut newest first.

Document budget decisions with the same rigour as growth decisions. If you defer a high-impact initiative because of cash timing, set a revisit date and trigger metric. Otherwise quarter-end panic repeats the same deferral without ever catching up.

Constraint framework names the bottleneck. Prioritisation ranks how to attack it. Without constraint context, prioritisation becomes abstract scoring of random ideas. With constraint context, every score answers a sharper question: does this move the limiting metric soon enough to matter?

When leadership proposes a new initiative, ask which constraint it serves and which metric it will move within ninety days. If answers are vague, defer or kill the initiative. This habit protects teams from executive shiny objects without requiring constant debate.

Review the backlog monthly with finance present when budget pressure exists. Prioritisation without budget context produces roadmaps nobody funds. A fifteen-minute budget alignment at the end of each quarterly scoring session prevents fantasy planning.

Prioritisation value compounds when decisions survive personnel changes and memory fade. Record each quarterly scoring session with date, participants, constraint statement, ranked initiatives, deferral reasons and explicit kills. Future leadership should understand why TikTok waited without reopening the same debate from scratch.

Link each active initiative to a single primary metric and a review date. Example: landing page test on commercial HVAC installs, primary metric qualified enquiry rate, review date four weeks from launch. Documentation without review dates becomes archive clutter. Review dates force accountability.

When initiatives complete, capture outcome versus estimate in the same log. Over time your organisation builds calibration on impact estimation. Teams that never close the loop keep scoring from gut feel and vendor optimism.

Share the decision log with finance when budget conversations arise. Prioritisation framed as evidence-based sequencing earns budget protection better than marketing defending every line item ad hoc.

Constraint shifts should trigger reprioritisation, not panic. If qualified volume recovers but estimating backlog explodes, the active initiative list must shift toward capacity and qualification even if media tests were planned. Use a formal mid-quarter review rather than hallway overrides that confuse agencies and staff.

Pause in-flight work that no longer serves the constraint when evidence is clear. Sunk cost attachment keeps teams optimising landing pages while jobs slip in the field. Leadership permission to stop is part of prioritisation discipline.

Communicate constraint changes to external partners the same day internal decisions land. Agencies continuing to optimise for lead volume after you declared a qualification constraint waste spend and trust. A short written update beats assuming partners noticed the shift.

Do not reprioritise weekly without new data. Mid-quarter changes should cite metric movement or operational events, not anxiety. Whiplash destroys test validity and morale. Two structured adjustments per quarter plus crisis exceptions is a sensible default for most operators.

List every active growth initiative across marketing, sales and operations. Mark which attack the current constraint. Pause one non-aligned item immediately. Reassign hours to the top-ranked aligned item.

Score the top five aligned initiatives on impact, confidence and dependency using ranges and notes, not gut feel alone. Produce a forced rank one through five. Name owners and primary metrics for the top three.

Share the one-page roadmap with your agency or internal marketing lead. Ask them to map their work to your sequence or explain mismatches. Growth prioritisation framework succeeds when external partners stop selling random tactics into an unfocused void.

Start a simple decision log document with today's date, current constraint sentence and what you chose not to do this quarter. One page is enough if you maintain it monthly.