Hypothesis-Driven Workplans

Workplans that start from an answer: a day-one hypothesis, analyses mapped to it with sources, owners and dates, weekly answer rewrites, and stop rules that keep effort on what changes the recommendation.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Hypothesis-Driven Workplans, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

📋 Management Consulting

Hypothesis-Driven Workplans

Turning hypotheses into a workplan: analyses needed, data sources, owners, dates and an early answer that gets revised as evidence comes in.

  1. Day-one answer to the key question
  2. Client decision the workplan must support
  3. Writing hypotheses that can be proven wrong
  4. Hypothesis to analysis mapping grid
  5. Workplan file with standard columns
  6. Data source named for every analysis
  7. One owner and one date on every line
  8. Prioritising analyses by impact on the answer
  9. Workplan sign-off with the engagement manager
  10. Three-times-weekly workplan check-in
  11. Weekly hypothesis status review
  12. Evidence log tied to hypotheses
  13. Friday rewrite of the current answer
  14. Workplan change log and re-plan rule
  15. Stop rule for analyses that cannot change the answer
  16. Data arrival and dependency tracker
  17. Monthly personal workplan retrospective
  18. Weekly capacity check against the workplan
  19. Weekly hypothesis practice on listed companies
  20. Analysis specs a colleague can run alone
  21. Calibrating your analysis effort estimates
  22. Rough first cuts before full analyses
  23. Guarding against confirmation bias in the evidence
  24. Matching hypothesis types to analysis types
  25. Status lines that say what was learned
  26. Choosing the workplan tool for the team
  27. Exploration period or hypothesis from day one
  28. Cutting the workplan for a shortened timeline
  29. Standard of proof for each hypothesis
  30. Replacing a refuted lead hypothesis
  31. Gating analyses that depend on earlier results
  32. Triage for client requests outside the hypotheses
  33. Audit of analyses that never reached the deck
  34. Partner problem-solving session on the workplan
  35. Midpoint answer check before the interim review
  36. Workplan reset after the interim review
  37. Final fortnight evidence gap close-out
  38. Hypothesis post-mortem after the engagement
  39. First workplan lines as a new analyst
  40. Associate owning a workstream workplan
  41. Integrated workplan across workstreams
  42. Two-week diagnostic sprint workplan
  43. Team-of-one workplan for solo engagements
  44. Internal strategy team workplan
  45. Distributed team workplan across time zones
  46. Commercial due diligence workplan
  47. Survey and market test lines in the workplan
  48. Competing hypotheses under high uncertainty
  49. Coaching a team in hypothesis-led planning
  50. Red team challenge of the lead hypothesis

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Day-one answer to the key question

Within the first two days of an engagement, writing down what you think the answer is, in one sentence with a number attached, gives the whole team something to test instead of a topic to explore. The early answer will be partly wrong, and that is the point: a wrong answer stated clearly gets corrected in a week, while no answer drifts for a month.

First tasks

  • Rewrite the key question in one sentence and check it with the manager
  • Write the one-sentence answer you would give if asked today
  • List the three to five things that must be true for that answer to hold
  • Save the answer as version one with today's date in the workplan

Client decision the workplan must support

A workplan built to understand the market never ends; one built to help a named executive decide whether to enter that market before a board date has a natural finish line. Writing down the decision, who makes it, by when, and what they would need to see to decide makes every later prioritisation call easier.

First tasks

  • Write the client decision as a choice between two or three options
  • Ask the manager who makes the decision and by what date
  • List the criteria the decision-maker has said matter to them
  • Link each top-level hypothesis to one of those criteria

Writing hypotheses that can be proven wrong

Most weak workplans start from hypotheses that cannot fail, such as 'costs could be reduced' or 'there may be growth in Asia'. Rewriting each one as a specific claim with a threshold, for example 'procurement spend is at least 8 percent above the peer median', tells you exactly what analysis to run and what result would kill it.

First tasks

  • Mark each current hypothesis as specific, vague or untestable
  • Add a direction, a size and a scope to every vague hypothesis
  • Write the result that would disprove each hypothesis beside it
  • Walk the rewritten list through with the manager in ten minutes

Make it yours.

Install Hypothesis-Driven Workplans, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.