Even the best business case content will suffer if the team works chaotically, files are a mess, and nobody trusts the model. This chapter is about how you run the work: collaboration rhythms, clean versioning, model governance, and a simple workflow you can reuse in every case.
25.1 Collaboration Rhythms and Roles
Think of a business case as a small, time-boxed project. You need a clear “who does what” and a steady cadence.
Core roles
You may not have all of these on every case, but you should know who is playing which hat:
- Sponsor / Economic Buyer
- Owns the problem/opportunity and ultimate outcomes.
- Sets direction, resolves cross-functional conflicts, engages peers.
- Case Lead (overall owner)
- Orchestrates everything: storyline, content, analysis, and pack.
- Single point of contact for sponsors and reviewers.
- Finance Partner
- Co-owns the model structure and economics.
- Validates assumptions, accounting treatment, and investment metrics.
- Workstream Leads (Tech, Ops, Commercial, Risk/Compliance, Data, Change)
- Own inputs and logic for their domain (costs, benefits, risks, dependencies).
- Approve how their content is represented in the case.
- Analyst / Model Owner
- Builds and maintains the financial model and key exhibits.
- Implements scenarios, sensitivities, and QA checks.
- PMO / Coordinator (for larger cases)
- Manages schedule, meetings, actions, version control hygiene.
- Ensures the team follows the workflow and checklist.
- Manages schedule, meetings, actions, version control hygiene.
In small cases, one person may wear several hats. It’s still worth naming them explicitly.
Collaboration rhythms
A simple, robust rhythm for a typical 3–6 week effort:
- Weekly “case working session” (60–90 minutes)
- Attendees: case lead, finance, workstream leads, analyst.
- Focus: decisions, open issues, data gaps, storyline.
- Output: updated action list and owners.
- Twice-weekly quick huddles (15–30 minutes)
- Attendees: case lead + analyst + 1–2 key contributors.
- Focus: unblock data/model/exhibit issues.
- Sponsor check-in (30–45 minutes, weekly or bi-weekly)
- Focus: direction, trade-offs, political / stakeholder angles, ask and conditions.
- Pre-wire meetings (once per key stakeholder)
- As covered in Chapter 21: targeted sessions with finance, risk, architecture, etc.
Use recurring calendar slots to avoid “scheduling chaos.” It’s easier to cancel a session you don’t need than to find a new time under pressure.
25.2 Version Control and Document Hygiene
Nothing kills confidence faster than two different “final” packs in circulation. Version control doesn’t need to be complex, but it must be explicit and enforced.
Single source of truth
Decide for each artifact:
- Where it lives (e.g., a single shared drive folder or repo).
- Who owns it (case lead for documents, analyst for model).
- What is authoritative (never email attachments as the “master”).
Recommended structure:
- /01_Business_Case_Doc
- /02_Slides
- /03_Model
- /04_Appendices
- /05_Archive (old versions)
Version naming convention
Keep it simple and consistent, for example:
- ProjectName_CaseDoc_v0.3_draft_2025-11-21.docx
- ProjectName_Deck_v0.7_ExCoDraft_2025-11-24.pptx
- ProjectName_Model_v1.0_Decision_2025-11-28.xlsx
Rules of thumb:
- 0.x = working drafts.
- 1.0 = first decision-ready version.
- 1.1, 1.2… = post-decision refinements or updated cases.
Only the owner updates version numbers. Contributors make comments or propose changes, not parallel “v0.9b” files.
Document hygiene basics
- Every main file should have:
- Title / initiative name.
- Owner (role and person).
- Version and date.
- Status (Draft / For Review / Decision Version).
- Avoid “Franken-packs”:
- Remove unused slides and backup drafts from the decision pack; keep them in the archive.
- Double-check that all template boilerplate (old logos, wrong project titles) is updated.
- Keep email light:
- Share links, not attachments, wherever possible.
- If you must attach, clearly state which version you are sharing and where the master lives.
25.3 Model Governance and Auditability
The model is often the most sensitive artifact. Treat it like code with light-touch governance.
Ownership and access
- Model owner: one person responsible for structure, logic, and QA.
- Finance approver: senior finance person who signs off economics.
- Access model:
- Edit rights: model owner + 1–2 deputies + finance.
- View rights: broader team.
- Avoid “everyone edits” models.
Structure and standards
At minimum:
- Separate Inputs / Assumptions from Calculations from Outputs.
- Use a clear sheet layout (e.g., 01_Guide, 02_Assumptions, 03_Baseline, 04_Costs, 05_Benefits, 06_CashFlow_NPV, 07_Sensitivities, 08_Checks, 09_ChangeLog).
- Standard formatting convention (e.g., yellow cells = inputs, grey = formulas, blue = links).
Change logging
Maintain a simple change log sheet:
- Date
- Author
- Version
- Summary of change (e.g., “Updated adoption ramp per pilot results; adjusted NPV from 32 to 27m”).
This makes red-teaming and later audits much easier.
QA and review
Build in:
- Automated checks on the Checks tab:
- Totals reconcile.
- No negatives were impossible (e.g., negative FTE).
- NPV recomputes correctly when you zero out benefits.
- Peer review: another analyst or finance controller walks through structure and top calculations.
- Stress-tests: set major drivers to extremes (e.g., zero benefits) and check that outputs change logically.
For large cases, treat model sign-off as a formal step (recorded email or note: “Finance has reviewed v1.0 model; OK for decision use”).
25.4 Step-by-Step Collaboration Workflow Guide
This is a reusable “how we work” sequence for building a case with a team.
Step 1 – Kick-off and scoping (Day 1–2)
Confirm:
- Problem/opportunity and decision required.
- Sponsor, case lead, finance partner, and initial workstream leads.
- Timeframe (when does the decision need to be taken?).
Agree on:
- Core deliverables (memo, deck, model, appendices).
- Collaboration tools (where files live, what you use for chat, what you use for tasks).
- Meeting rhythm (weekly working session, sponsor check-ins, target red-team date).
Capture this in a short Case Charter email or one-pager.
Step 2 – Work breakdown and ownership (Day 2–3)
- Break the case into work components aligned to chapters:
- Context & baseline.
- Options & economics.
- Costs & resourcing.
- Risks & dependencies.
- Implementation & governance.
- KPIs & benefits tracking.
- Assign each component:
- Content owner (typically a workstream lead).
- Contributor(s) (analysts, SMEs).
- Dependencies between components.
Build a simple RACI or ownership table; keep it to one page.
Step 3 – Skeleton first, then fill (Week 1)
Case lead drafts:
- Outline of the memo/deck (section headings, ~1–2 bullets per section).
- Initial list of required exhibits and model views.
Team reviews and aligns on:
- Storyline.
- Which analyses are truly necessary.
Only after this should people dive into heavy modeling or exhibit production.
Step 4 – Parallel content and modeling (Week 1–2)
- Workstreams collect inputs (data, quotes, constraints) and draft content.
- Analyst/finance build the first working model using best-available inputs.
- Case lead iterates storyline as early insights emerge.
Weekly working session:
- Review early model outputs and sanity.
- Decide where more precision is needed vs “good enough.”
- Capture and assign all follow-ups.
Step 5 – Integrate and challenge (Week 2–3)
- Produce a first integrated draft of the memo/deck + model.
- Run internal reviews:
- Finance for economics.
- Risk/compliance and architecture for feasibility and controls.
- Sponsor for directional alignment.
- Conduct a red-team session (as in Chapter 21) to stress-test.
Track issues in a shared log (spreadsheet or tracker) with severity and owner.
Step 6 – Refine for decision (Week 3–4)
- Address must-fix issues from red-team and sponsor.
- Clean up structure, exhibits, and language; remove orphan content.
- Freeze Decision Version v1.0 of model and case pack.
At this point, start tailoring variants (Board, ExCo, Tech, Regulator) if needed, all based on the same core numbers.
Step 7 – Approval and hand-off (decision week)
- Run formal approval meetings per your governance path.
- Document decision, funding, and conditions.
- Package final case + model + appendices into an archive bundle.
- Hand off to program/implementation team with:
- Roadmap and milestones.
- Benefits register and KPIs.
- Risk register and gate criteria.
The workflow is the same in each case; only the content changes.
25.5 Tooling & Hygiene Checklist
Use this checklist to keep teaming and tools under control.
Team & roles
- Sponsor, case lead, finance partner, and model owner are explicitly named.
- Workstream leads are assigned for Tech, Ops, Commercial, Risk/Compliance, Data, and Change (as relevant).
- Time commitments for critical roles are realistic and discussed with their managers.
Collaboration tools
- There is a single canonical location for:
- Documents/memos.
- Slides.
- Model.
- Appendices.
- Access rights are appropriate (edit vs view).
- There is one agreed task tracker (even a simple list) for actions and owners.
Version control
- File naming conventions include project name, artifact type, version, and date.
- Only the designated owner updates version numbers.
- Older versions are archived in a dedicated folder; decision versions are clearly labeled.
- Emails share links to the master location, not “mystery attachments” with new names.
Model governance
- The model has clear structure: guide tab, assumptions, baseline, costs, benefits, cash flow & NPV, sensitivities, checks, change log.
- Inputs, calculations, and outputs are visually distinct.
- QA checks exist and have been run; peer review and finance review are complete.
- A change log captures major edits, with dates and authors.
Meeting rhythm
- Weekly case working session in calendars (with fixed agenda).
- Sponsor check-ins and key pre-wire sessions are scheduled early.
- Red-team review has a slot and invitees defined.
- Decision meeting dates and pack deadlines are known and backward-planned.
Hygiene before sharing
- Every file shows correct title, owner, version, and date on the cover/first page.
- No leftover placeholder slides, old logos, or irrelevant templates remain.
- Option names, KPI labels, and risk names are consistent across all artifacts.
- Confidentiality markings (if needed) are correctly applied and distribution lists are checked.
If you can tick these boxes, you’ll not only have a strong business case—you’ll have a team and working model that you can reuse, refine, and scale for every major decision that follows.
