Every serious consulting engagement ends with a Ways of Working document. It ships alongside the strategy deck, usually runs thirty to forty pages, describes who does what by when, and gets filed in a shared drive where nobody reads it again. This is the open secret of consulting deliverables: the operational manual is the least-read artefact in the entire engagement package.
And yet clients pay for it, expect it, sometimes grade the engagement on it. Why? Because the Ways of Working document isn't actually an operational manual. It's an emotional hook and a sales asset, and if you design it without understanding that, you're leaving both client satisfaction and module-two revenue on the table.
Here's the realisation that changed how we designed ours.
The document has two jobs
The first job - the declared one - is genuinely useful reference material. When the Regional MD six months in can't remember why the territory boundaries were drawn the way they were, the Ways of Working document answers in decision-memo form: here's what we considered, here's the data that drove the call, here's what would cause us to revisit it. When the newly appointed Commercial Director needs to understand the commercial rhythm - what happens weekly, monthly, quarterly, annually - the document gives them a structured playbook. These uses are real but infrequent. They happen at transitions, handovers, and moments of doubt. The document needs to be good enough to survive those moments, but that's not what makes it worth building well.
The second job - the undeclared one - is to sell the next module. An RMD who flips to their own page and sees themselves described accurately feels understood. The description is specific, not generic - it captures the way an excellent RMD thinks about territory trade-offs, how they weight coverage versus margin, what keeps them up at night during a distributor transition. Not management advice in the abstract, but the kind of specificity that makes them think "this consultant actually understands my job." The natural follow-up question, minutes later, is the one the document is designed to plant: "how do I actually track whether my team is doing this?" That's exactly what Modules 2 and 3 answer. Module 2 is the JBP workspace where weekly, monthly, and quarterly rhythms are tracked against commitments. Module 3 is the field execution layer where the DSR's "day in the life" becomes measurable performance against archetype-weighted targets.
The document sells the next module better than any sales deck could, because it plants the question in the client's own mind at the moment when they're most receptive - right after delivery, when the engagement has proven its value and they're wondering how to make it stick.
Design implications
Once you understand the document's second job, the design follows. The spine is role-by-role: one page per key role - Commercial Director, Regional MD, RTM Manager, Distributor Principal, Distributor Sales Manager, DSR, Territory Manager, Field Research Analyst. Seven or eight roles, one or two pages each. That's fifteen pages of role content alone - plenty of weight to carry the rest of the document.
Each role page follows a consistent structure. An avatar (illustrated, not photographic - consistent style across all roles, visually unified). A bold "What Good Looks Like" headline. Three columns: Must-Win Battles, Day in the Life, What Module 2/3 Tracks. A pull quote in large type - something an excellent person in that role would actually say, not inspirational poster language. The pull quote is the most-read element on the page. Get it wrong and the page falls flat. Get it right and the RMD forwards the document internally.
The "Must-Win Battles" column is grounded in the actual engagement data. Generic best-practice advice reads as filler. Specific battles - "Achieve 67% coverage in Territory Alpha by Month 6", "Replace the underperforming East Java distributor by Week 16 with coverage parity protected" - read as tailored work. The distinction is enormous. Generic advice treats the reader as a category; specific advice treats them as a person.
The "Day in the Life" column is where the document earns its right to exist. It describes a typical week for the role in concrete terms: Monday, the DSM reviews the weekend sell-out numbers with the team; Tuesday morning, they're in the field with two DSRs on routes that include one challenging outlet each; Wednesday, JBP tracking meeting with the Commercial Director; Thursday, competitor intelligence gathering and inventory planning; Friday, weekly report submission. Not prescriptive, not rigid - but specific enough that it reads as how the work actually happens, not as an idealised diagram.
The "What Module 2/3 Tracks" column is where the document sells without selling. It's presented as reference information, factually stating what the platform measures. "Weekly: sell-out volume against target per outlet, visit completion rate, shelf share at audited outlets." "Monthly: archetype coverage progression, ghost outlet reconciliation, DSR productivity index." Read as reference, it's information. Read as preview, it's the Module 2 and Module 3 product brochure, delivered with the credibility of a deliverable the client has already paid for.
The cultural reason most consulting firms don't do this
Most consulting firms produce Ways of Working documents that are either generic (McKinsey-style management frameworks applied to the client's context) or exhaustively specific (BCG-style process maps with thirty swimlanes). Neither version works for the second job. The generic version reads as filler and doesn't sell anything. The exhaustive version is too detailed to be read and too operational to be emotional. Neither plants the "how do I track this" question because neither describes what tracking would actually look like.
The reason is structural. Consulting firms sell projects, not products. Each Ways of Working document is a one-off artefact produced by a project team and filed away. There's no incentive to design it as a sales asset for a product the firm isn't selling. A vertical SaaS platform has the opposite incentive: every engagement deliverable should either prove the current module's value or plant the seed for the next one. The Ways of Working document sits in a uniquely privileged position to do both.
The test that matters
Here's the test for whether your Ways of Working document is working as a sales asset: when you hand the draft to the RMD for review, do they ask whether it can be shared more widely inside the organisation? If yes, you've built it right. They're about to circulate the document to people who don't yet know about the engagement, which is the exact audience the next module needs to reach. If they file it in a shared drive without comment, you've built reference material. Useful, but a missed opportunity.
Reference material is a cost of doing business. A sales asset is a flywheel.