The single most common consulting mistake is solving the wrong problem confidently. Before you do any analysis, any research, any work — you need to know exactly what problem you're actually solving. That takes longer than you think, and it is worth every minute.
The Problem as Stated vs. The Real Problem
A client says: "We need to increase social media engagement." That's a symptom. The real problem might be declining season ticket renewals, poor brand awareness among Gen Z, a weak content strategy, or all three. If you build a social media plan without diagnosing the underlying issue, you've given them a solution to the wrong problem.
Use the first client meeting to listen more than you speak. Ask "why" more than once. Ask what success looks like. Ask what they've already tried. Ask what they're afraid might be true. The answers will reshape the problem completely.
The 5 Whys — A Fast Root Cause Tool
State the symptom: "Ticket sales for weeknight games are down 18% year-over-year."
Why? "Attendance for those games is down." Why? "Fans say they can't make it after work." Why? "Game start time is 7pm and commute is difficult." Why? "No direct transit from downtown." Root cause: access, not interest.
Your recommendation (shuttle partnership, earlier start times) is now grounded in the real problem — not the surface symptom.
Writing a Problem Statement
Before your team starts any work, write a single-sentence problem statement and get the client to confirm it. This is the most important sentence in the engagement.
Example: "How might we redesign the weeknight game experience for young professionals in Portland so that attendance increases 10% by next season?"
Scope Discipline
Once you have a problem statement, your team's job is to stay inside it. Scope creep is when the project gradually expands beyond what was agreed — and it kills teams. Every time someone says "and we could also look at…" in a team meeting, ask: does this serve the problem statement? If not, park it.
Do
- Confirm your problem statement with the client in writing
- Ask "why" at least 3 times before accepting a problem framing
- Define what's in scope and out of scope explicitly
- Revisit the problem statement when findings surprise you
Don't
- Jump to solutions before the problem is clear
- Accept the client's framing without questioning it
- Let scope expand silently — name it and decide
- Start building slides before you know what you're arguing
Research is how you earn the right to make recommendations. Without it, you're just giving the client your opinion — and they didn't hire you for your opinion. They hired you for evidence-backed insight.
Primary Research
You gather this yourself — surveys, interviews, focus groups, observation. Primary research is the most valuable because no competitor has it. In sport consulting, this often means talking to fans, front office staff, or conducting competitive analysis.
- Stakeholder interviews with open-ended questions
- Fan surveys via email, event intercepts, or social
- Competitive benchmarking (attend games, analyze digital)
- Secret shopping — experiencing the product yourself
Secondary Research
Existing sources — industry reports, academic studies, news coverage, published data. Fast and cheap, but generic. Secondary research gives you context and comparisons. It tells you what's true for the industry, not what's true for your specific client.
- Industry reports (SportsPro, Front Office Sports, Sportico)
- Academic research via Gonzaga library databases
- Competitor social/digital analysis
- Market sizing data (Statista, IBISWorld)
Research for Evidence, Not Confirmation
The most dangerous moment in a consulting engagement is when your team decides what the answer is before the research is done. Once you've pre-decided, every piece of evidence starts looking like confirmation. This is confirmation bias — and it produces recommendations that feel right but aren't grounded in reality.
The antidote is to actively search for evidence that contradicts your hypothesis. If your hypothesis is "weeknight games need earlier start times," go find data suggesting that start times aren't the issue. If you can't disprove it, your confidence in the hypothesis goes up legitimately.
"The goal of research is to find the truth, not to prove your hypothesis. If the data tells you something surprising, that's the most valuable thing you'll produce."
Evaluating Source Quality
Not all sources are equal. In Q&A, you will be asked where something came from. Know the answer — and know why it's credible.
A stat from an ESPN article is not the same as a stat from a Sportico earnings analysis. Know the difference and cite accordingly.
Research produces data. Analysis produces findings. But synthesis — connecting findings into a coherent point of view — produces insight. Insight is what consulting clients actually pay for. It is the hardest skill to develop and the one that separates good consultants from great ones.
Data → Finding → Insight → Recommendation
These are four different things. Most student consultants stop at findings. Clients need recommendations, and recommendations require insight — the "so what" that connects what you found to what they should do.
The Insight Pyramid
Data: "Weeknight game attendance is down 18%. 63% of surveyed fans cite difficulty arriving before 7pm."
Finding: "Access, not interest, is the primary barrier to weeknight attendance."
Insight: "The organization is losing a willing audience to a solvable logistics problem — not a preference shift."
Recommendation: "Pilot a downtown shuttle partnership and a 6:30pm start for Tuesday games in Q1."
The "So What?" Test
After every finding, ask "so what?" out loud. If you can't answer, it's not a finding worth including. If the answer is obvious, it's not an insight — it's a data point. The "so what" that surprises you, or that contradicts what the client expected, is almost always the most valuable thing in your deck.
Simplicity as Mastery
Consultants who are still learning fill slides with everything they found. Consultants who have mastered synthesis show only what matters. Cutting findings that are interesting but not actionable is hard. Do it anyway. The client's attention is finite — every minute they spend on a weak insight is a minute not spent on the one that will change how they run their business.
Before you can communicate clearly, you have to think clearly. Structured thinking frameworks help you organize complexity into a form that's both rigorous and communicable — so your recommendations have a spine, not just a list of ideas.
MECE Thinking
Mutually Exclusive, Collectively Exhaustive. When you break a problem into parts, the parts shouldn't overlap and they should cover everything. This applies to your issue tree, your recommendation buckets, your slide categories.
Test: if you combined all your parts, would they add up to the whole problem? Do any overlap? Fix it before you build anything on top of it.
Issue Trees
Break your main question into sub-questions, then sub-sub-questions, until each branch is answerable with research. The tree makes sure you haven't missed anything, and it maps your research plan.
Example: "Why is fan engagement declining?" branches into Attendance, Digital, In-Stadium Experience, and Post-Game Retention — each of which branches into more specific questions.
The Pyramid Principle
Every argument should be structured with the conclusion first, followed by the supporting arguments, followed by the evidence. This is the opposite of how most people naturally write — but it's how executives read. They want to know where you're going before they invest attention in how you got there.
Slide body = your 2–3 supporting points
Appendix = your evidence for anyone who wants to verify
If your headline is "Attendance Analysis" rather than a conclusion, rewrite it.
Six people in a team doesn't mean the work is divided six ways and reassembled. It means the thinking is better because six perspectives challenge each other. The teams that produce the best work are the ones who know how to disagree productively — and then commit to a shared direction.
Role Clarity
Ambiguity about who owns what is the most common cause of team conflict. At the start of the engagement, assign clear ownership for every workstream — research, analysis, client communication, slide production, presentation prep. Owners don't have to do it alone, but they're accountable for it getting done.
The Project Manager Role
The PM in GSCG isn't just a scheduler. They protect the team's time, manage the client relationship, and make the call when the team is stuck. Good PMs spend more time asking "what do you need to move forward?" than telling people what to do.
Productive Disagreement
When team members disagree on a finding or recommendation, that tension is valuable — it means the issue isn't obvious. The wrong response is to suppress it for the sake of harmony. The right response is to make the disagreement explicit, identify what evidence would resolve it, go get that evidence, and then decide.
If you can't resolve it with evidence, escalate to the PM. The worst outcome is a hedge — a recommendation that tries to be everything and means nothing.
Giving and Receiving Feedback
Feedback in GSCG should be specific, timely, and focused on the work — not the person. "This slide is hard to follow because the headline doesn't match the chart" is useful. "This isn't good" is not. When you receive feedback, don't defend. Listen, ask clarifying questions, then decide whether to act on it.
Week 3–6: Working sessions 3x/week — review, challenge, iterate
Week 7: Presentation rehearsals only
Week 8: Delivery + team debrief within 48 hours
Your deck is not a report. It is a visual aid for a conversation. Every slide should serve one idea, and that idea should be clear from the headline alone. If your audience has to read the slide to understand it, the slide has failed.
The Golden Rule: One Idea Per Slide
Every slide has one job. If you find yourself writing "and also…" on a slide, that's a second slide. Splitting ideas across slides forces you to be clear about what each idea actually is — and it makes the deck far easier to follow.
Headlines That Tell the Story
The headline is the most important text on the slide. It should be a complete sentence that states your conclusion — not a label for what's on the slide. A reader who only reads your headlines should walk away with your full argument.
Strong Headlines
- "Gen Z fans prioritize experience over price — and are willing to pay for it"
- "Merchandise revenue is 34% below peer organizations with similar attendance"
- "Three fan segments drive 80% of digital engagement"
Weak Headlines
- "Fan Survey Results"
- "Merchandise Analysis"
- "Digital Engagement Overview"
Data Visualization
Every chart needs a "so what." Annotate the key finding on the chart — don't make your audience find it. Use color sparingly: one highlight color for the point you're making, everything else muted. Label axes clearly. Never use 3D charts.
- Bar charts for comparisons
- Line charts for trends over time
- Scatter plots for relationships between variables
- Tables only when precision matters more than pattern
Visual Hierarchy
The eye goes to size, then color, then position. Design accordingly. Your headline is biggest. Your key data point is highlighted. Supporting context is smaller and muted. Everything on the slide should feel intentional — if you can't explain why something is the size and color it is, simplify.
- Use 2–3 fonts maximum (headline, body, data label)
- Maintain consistent margins and spacing
- One accent color per slide for emphasis
- White space is your friend — don't fill every pixel
The Narrative Arc
A deck should read like a story: situation → complication → resolution. The client knows their situation. The complication is what your research revealed. The resolution is your recommendation. Every slide should advance that arc. If a slide doesn't move the story forward, ask whether it belongs in the deck or the appendix.
The final presentation is the moment everything you've built gets tested in real time. The deck is finished. The research is done. Now it's about conveying your findings with confidence, handling questions with honesty, and leaving the client with complete trust in your work.
Know Your Material — Not Your Script
Reading from slides is the fastest way to lose a room. Your slides are the visual aid; you are the content. Know your argument well enough to talk to any slide without looking at it. This only comes from rehearsal — multiple rounds of it, ideally with someone asking hard questions.
Opening Strong
The first 60 seconds set the frame for everything that follows. Open with the problem statement and a one-sentence preview of your recommendation. Don't open with introductions, housekeeping, or "so today we're going to…" Get to the point immediately. You'll earn their attention by respecting their time.
That's 30 seconds. Everything else is proof.
Handling Q&A
Q&A is not an attack. It's how executives engage with material they find interesting. Hard questions mean they're taking your work seriously. Listen to the full question before responding. If you don't know the answer, say so — then offer to follow up. Never speculate. Never be defensive.
Managing Nerves
Nerves are normal and largely invisible to your audience. Slow down — nervous speakers rush. Pause after key points. Make eye contact with individuals, not the room. Physical presence (posture, stillness, controlled gestures) signals confidence even when you don't feel it.
Rehearsal Protocol
- Run the full deck out loud at least 3 times before the presentation
- Time yourself — you should have 5 minutes buffer
- Have someone ask the hardest questions they can think of
- Know your appendix — anticipate what they'll want to dig into
- Run once with the actual technology you'll use on the day
Every email, every Teams message, every status update is a data point the client uses to assess your professionalism. Communication doesn't start the day of the presentation — it runs through the entire eight weeks. How you communicate is as visible as what you produce.
Client Emails
Short, clear, and purposeful. State your ask or update in the first sentence. Use bullet points for multiple items. End with a clear next step or call to action. Re-read before you send — every time.
- Subject line that states the purpose
- Lead with the bottom line, not the background
- One email, one topic — don't combine unrelated items
- End with a clear next step and timeline
Status Updates
Keep clients informed without overwhelming them. A brief weekly update — what the team accomplished, what's coming next, and any questions you need answered — maintains trust and prevents surprises. The worst moment in a consulting engagement is when the client feels left in the dark.
- Weekly written update, 4–6 bullet points maximum
- Surface issues early — don't wait for the final presentation
- Be specific about timelines and deliverables
- Flag decisions that need client input with a clear ask
Internal Team Communication (Teams)
The same professionalism applies internally. Keep Teams organized — use channels by workstream, pin important documents, and maintain a shared agenda for every working session. Informal is fine; disorganized is not. When a new team member looks at your channel, they should be able to get up to speed in 10 minutes.
Asking for What You Need
Most of the access you need — data, client contacts, internal reports — requires asking for it directly and clearly. Be specific: "We need last season's ticketing data broken down by section and day of week for analysis. Can you connect us with whoever manages that, or share a report format you already have?" Vague requests get vague responses.
The engagement isn't over when you leave the final presentation. It's over when you've honestly assessed what you learned — and done something with that assessment. The consultants who improve fastest aren't always the most talented. They're the ones who take this step seriously.
The Team Debrief (After Action Review)
Within 48 hours of the final presentation, hold a team debrief. Not a celebration — a real conversation. The goal is to identify what the team should keep doing, stop doing, and start doing. The debrief is most valuable when it's honest, specific, and not defensive.
After Action Review Format
What did we intend to accomplish? Restate the original problem statement and goals.
What actually happened? Honest account of the process and the output — what went well, what didn't.
Why did it happen? Root causes — not blame. Process issues, communication gaps, skill gaps.
What do we do differently next time? Specific, actionable changes — not "communicate better." "Hold a kickoff scoping session in week one" is actionable.
Individual Self-Assessment
Beyond the team debrief, take 30 minutes to write your own honest assessment. What was your best contribution? Where did you hold the team back? What skill felt most underdeveloped? What would you do differently? This isn't shared unless you choose to — it's for you.
The students who improve most across GSCG engagements are the ones who take this question seriously: What's the honest gap between where I am and where I want to be as a consultant?
Building Your Consulting Identity
Over multiple engagements, you'll start to notice patterns — where you consistently add the most value, which types of problems energize you, what kind of client relationships you're best at. Pay attention to those signals. They're the early indicators of what kind of consultant you're becoming.
The GSCG experience is designed to accelerate this. But the accelerator only works if you're paying attention.
