---
name: consulting-methodology
description: Guides AI through standard consulting engagement process, from discovery to deliverables
version: 1.0.0
author: Your Name
tags:
  - consulting
  - methodology
  - client-engagement
---

# Consulting Methodology

> This skill helps AI assistants follow your consulting methodology when helping with client projects.

## Instructions

When assisting with consulting projects, follow these phases:

### Phase 1: Discovery
- Ask clarifying questions to understand the client's current state
- Identify pain points and root causes, not just symptoms
- Document stakeholders and their priorities
- Establish success metrics before proposing solutions

### Phase 2: Analysis
- Structure the problem using frameworks (MECE, 5 Whys, etc.)
- Gather relevant data points before making recommendations
- Consider both quantitative and qualitative factors
- Identify quick wins vs. strategic initiatives

### Phase 3: Recommendations
- Lead with the "so what" - business impact first
- Present options with trade-offs, not just one solution
- Include implementation considerations
- Anticipate objections and address them proactively

### Phase 4: Deliverables
- Use the pyramid principle: conclusion first, then supporting details
- Include executive summary for all documents
- Visualize data when possible
- End with clear next steps and owners

## Examples

### Good Discovery Question
"Before I suggest solutions, I want to understand: What does success look like for this initiative? How will you measure whether we've achieved it?"

### Weak Discovery Question  
"What problem are you trying to solve?" (Too vague, doesn't probe for metrics)

### Good Recommendation Format
"I recommend Option B because it delivers 80% of the value at 40% of the cost of Option A. Here's the trade-off: we'd delay the advanced features by 6 months. Given your Q2 budget constraints, this positions you to..."

## Best Practices

1. **Never jump to solutions** - Always complete discovery first
2. **Quantify impact** - Use numbers whenever possible ("reduces time by 40%" vs "saves time")
3. **Consider the audience** - Executives want bottom-line impact; operators want detailed steps
4. **Document assumptions** - Make your reasoning transparent
5. **Build buy-in** - Include stakeholder perspectives in recommendations

## Anti-Patterns to Avoid

- Presenting only one option ("take it or leave it")
- Burying the lead in lengthy context
- Using jargon without defining it for the audience
- Skipping the "why" behind recommendations
- Failing to address implementation risks