Your methodology is your product

Codifying your approach isn't documentation. It's product development for your practice. The 5-step process to turn what's in your head into defensible intellectual property.

I hear this objection often: 'My value is my judgment. You can't codify that.' Wrong. Your judgment is the product of patterns you've recognized across dozens of engagements. Those patterns can be codified. The process below takes about a week of distributed effort. The result is an asset that transforms your pricing, your ability to delegate, and the resale value of your practice.

Francis Beaulieu

Why this matters right now

According to David C. Baker, a consulting practice without codified intellectual property is worth zero at resale. With codified IP (named methodologies, diagnostic frameworks, proprietary tools), that same practice sells for 3 to 7 times annual revenue. Codification is not a documentation project. It's the construction of your practice's most valuable asset.

More immediately: a codified methodology lets you charge more (a named framework = a confidence premium), delegate (others can operate the process), and sell faster (the prospect understands your approach before meeting you).

Pricing: the price of a named framework

The action: Name your diagnostic process. Not a forced acronym. A name that describes what the client gets: "Operational Maturity Diagnostic," "Growth Readiness Assessment," "Flow Optimization Protocol." Present it as a proprietary framework in your proposals.

Why a name changes the price: Consumer psychology research, synthesized by Robert Cialdini in Influence, demonstrates that a named process is perceived as 30-40% more valuable than an identical unnamed process. The name signals structure, repeatability, and intellectual investment. "Our Pulse-12 Assessment" commands a premium that "our assessment" does not.

The trap: The name must be descriptive, not marketing. Avoid artificial acronyms and wordplay. The test: if a prospect has to ask "what does that mean?", the name is bad.

This week: Name your most-used process. Integrate the name into your next proposal. Observe the difference in the conversation.

Sales and business development: content that demonstrates the method

The action: Write an 800-1,000-word article that explains one step of your methodology in enough detail that the reader understands how you think, without revealing enough that they no longer need you.

The principle: Patrick McKenzie (patio11), in his essays on professional services, argues that the most effective business development content for consultants is content that shows the reasoning behind the method, not generic advice. An article titled "Why 70% of operational audits miss the real bottlenecks (and how we avoid it)" attracts qualified buyers who recognize the problem.

The formula: Common industry problem -> Why the standard approach fails -> Your different angle -> A glimpse of your method -> Measurable result from a case (anonymized). The reader finishes thinking "this person understands my problem better than I do."

This week: Identify the step in your methodology where your approach diverges most from the norm. Write the article. Send it to 10 targeted prospects.

From the Field

Robert, Saskatoon

I've been a project management consultant in the mining sector for 12 years. Every project turnaround engagement followed the same process: 72-hour assessment, identification of the 3 critical bottlenecks, 2-week recovery plan, 90-day coaching. But it was all implicit. In my head.

Last year, I spent two weeks documenting everything. The '72-Hour Intervention Protocol.' The 15 diagnostic questions. The 7 derailment patterns I observe in 90% of troubled mining projects. The triage criteria.

Three things happened. First, I was able to train a junior associate to conduct initial assessments. Second, prospects started choosing me because of the documented methodology rather than despite my higher price. Third, a private equity fund approached me to ask whether I'd license my methodology to their portfolio firms. I'd never considered it.

Collaboration networks: the codification partner

The action: Identify a trusted consultant in a complementary field. Propose a codification exchange: you document each other's methodologies by asking structured questions. You interview their method; they interview yours.

Why a partner matters: Amy Edmondson, in The Fearless Organization, documents that experts suffer from a "curse of knowledge": they no longer see the steps in their own process because those steps have become automatic. An external interviewer forces the articulation of what's implicit.

The format: 3 sessions of 90 minutes each. Session 1: "Walk me through the beginning of your typical engagement, step by step." Session 2: "When you reach [critical step], how do you decide what to do?" Session 3: "What are the failure patterns you recognize, and how do you avoid them?" Record. Transcribe. Structure.

This week: Contact a trusted consultant: "I'd like us to help each other document our methodologies. 3 sessions of 90 minutes each. Interested?"

Value creation: the 5 steps of codification

The action: Follow this 5-step process to codify your primary methodology.

Step 1: List the last 10 key decisions you made in an engagement. Not activities. Decisions. "I decided to start with field interviews instead of data analysis because..."

Step 2: Find the patterns. Group the decisions into categories. You'll see 3-5 recurring phases emerge in your approach.

Step 3: Name each phase. Give each a descriptive name and sequence them. You now have the skeleton of your framework.

Step 4: Document the decision rules. For each phase, write the criteria that make you advance, pivot, or dig deeper. "If X, then I dig deeper. If Y, I move to the next phase."

Step 5: Test with a real case. Apply the documented framework to your current engagement. Note the gaps between what the framework says and what you actually do. Adjust.

This week: Complete Step 1. List your last 10 engagement decisions. The rest will follow naturally.

The AI Accelerator

Practice scenario: you're an occupational health and safety (OHS) consultant for manufacturing companies.

1. Incident data analysis. Feed incident reports, near-misses, and CNESST data into Claude. Ask: "Identify recurring patterns, high-risk zones, and systemic causes behind the most frequent incidents." The AI surfaces correlations that manual analysis misses.

2. Regulatory compliance assessment. Import applicable OHS regulations and the client's prevention programs. The AI identifies compliance gaps, ranked by severity and likelihood of sanction. Each gap is accompanied by the exact regulatory reference.

3. Safe work procedure generator. For each high-risk task, feed in the task description, equipment used, and incident history. The AI drafts a structured safe work procedure with steps, required PPE, checkpoints, and emergency measures.

4. Training program builder. From the incident analysis and compliance gaps, the AI generates a prioritized training program: target audience, learning objectives, duration, instructional method, and measurement indicators per module.

5. Predictive incident dashboard. Feed historical incident data (type, location, time, conditions, employee experience) and ask the AI to model risk factors. "What combinations of factors best predict an incident?" The client shifts from reactive to targeted prevention.

AI: use AI to extract your implicit methodology

The action: Gather 5 proposals and 5 final reports from past engagements. Feed them into Claude (anonymized). Ask: "Analyze these 10 documents and identify: (1) the recurring steps in my process, (2) the types of deliverables I systematically produce, (3) the patterns in how I frame problems, (4) the differences between my proposals and my final deliverables (a sign of mid-engagement adaptation)."

Why this goes beyond basic AI use: You've been trying for years to articulate your method by thinking about it. AI finds it in your work artifacts. That's more reliable than introspection, because your documents reveal what you actually do, not what you think you do.

Research by Ethan Mollick at Wharton, published on One Useful Thing, shows that AI-assisted extraction of tacit knowledge (the knowledge an expert possesses but cannot spontaneously articulate) is one of the most underestimated professional AI use cases. AI detects patterns in your writing that you no longer see because they've become automatic.

The advanced process: After the initial extraction, ask: "Among these patterns, which are unique to my approach and which are industry standard?" The unique patterns are the core of your IP. The standard patterns are context. Codify the unique ones; reference the standard ones.

This week: Gather 5 documents from past engagements. Feed them into Claude. Read what the AI tells you about your own method. You'll be surprised.

Like what you read? Get this in your inbox every Tuesday.

By subscribing, you agree to receive a weekly newsletter from Cogni6 inc. (Quebec, Canada). You can unsubscribe at any time.

Free. No spam. Unsubscribe in one click.