For the last several weeks, we have focused heavily on the technical acceleration of your career. We explored how to integrate Artificial Intelligence into your workflow and set three distinct goals to automate your redundancy.
That was the science. Now, we return to the art.
You can be the most technically gifted analyst in your organization. You can write Python scripts that automate complex ETL pipelines and build dashboards that rival modern art. But if you cannot manage the human element of your work, you will fail.
The most common complaint I hear from data professionals is that they feel like “order takers.”
They are treated like a drive-thru window. A stakeholder pulls up, screams a request for a neat, well-defined menu item into the microphone, and the analyst scrambles to flip the burgers. This dynamic leads to burnout, resentment, and low-value work.
The solution is not to work faster. The solution is to change your operating model. You must stop acting like a technician and start acting like a consultant.
Over the next four newsletters, we are going to dismantle your current workflow and replace it with a professional consulting framework. We will cover how to manage intake, how to structure your thinking, how to ensure quality, and how to hand off work so you can actually go on vacation.
Today, we start with the most critical shift: Stop taking orders and start managing commitments.
The Core Concept: The Ask Behind the Ask
The difference between a junior employee and a senior partner is the ability to manage expectations. Managing and meeting client expectations are the governing principles of your identity as a consultant.
When you operate as an “order taker,” you accept expectations implicitly. A stakeholder asks for a number, and you say “okay.” In that moment, you have lost control. You have allowed the stakeholder to define the timeline, the complexity, and the definition of success.
You are not employed to simply produce on-demand analytics products from a menu. You are a strategist.
Stakeholders often do not know the solutions that would solve their challenges. They come to you with a “request”—the tactical data pull they think they need. But your job is to uncover the “Ask Behind the Ask.”
The “Ask Behind the Ask” is the real underlying challenge that motivated the request. If a sales leader asks for a massive list of consumer targeting data, the order taker pulls the list. The consultant asks, “What are we trying to solve?”
By getting to the underlying business problem, you can craft an appropriate solution rather than just fulfilling a request. This prevents you from building things that don’t matter. It ensures that you and your client have the same understanding of what will be delivered.
The Strategic Framework: Defining Commitments
To operationalize this mindset, you need a framework for “Defining Commitments.” You cannot simply start working. You must first define the box you are working inside.
1. The Proposal Protocol In a formal consulting engagement, expectations are initiated by a proposal document. You might think this is unnecessary for an internal data request. You are wrong. You need a “proposal,” even if it is just a concise email or a one-page summary.
This document serves a specific purpose: it creates a shared reality. It clearly defines deliverables and scope of effort at the outset of any engagement. Without this artifact, the deliverables are fluid. Fluid deliverables drown analysts.
2. Bifurcated Objectives Most analysts conflate what the business wants with what the analyst is doing. You must separate these into two distinct categories:
- Client Objectives: This defines what the client wants to achieve as a direct result of the engagement (e.g., “Increase Q3 retention by 5%”).
- Engagement Objectives: This defines what the Firm (you) has committed to the client (e.g., “Identify the top three churn drivers and build a retention monitoring dashboard”).
You cannot commit to the Client Objective. You cannot guarantee retention will go up. You can only commit to the Engagement Objective. If you do not distinguish these, you will be blamed when the business metric doesn’t move, even if your analysis was perfect.
3. The Scope Sovereign Once you begin, the enemy is “scope creep.” You must guard against this relentlessly.
Stakeholders will always ask for “just one more view” or “just one more cut of the data.” If you have not clearly defined the deliverables at the outset, you have no grounds to say no. Revisit the original proposal and agreed-upon deliverables regularly.
A client’s interest in work outside the established scope should be viewed as a business development opportunity. It is a chance to say, “We can definitely do that. That is a new project. Let’s scope that out separately.”
The Analyst’s Playbook
You are likely thinking, “I can’t write a 10-page contract for every SQL query.” You don’t have to. Here is how you apply high-level consulting essentials to your daily data work.
1. The Six-Word Interjection When a stakeholder approaches you with a predefined solution or a “data pull,” do not write it down. Stop them. Ask six simple words:
“What are we trying to solve?”
This forces the conversation away from the order and toward the “Ask Behind the Ask.” It allows you to analyze the client’s current situation and issues before you commit to work.
2. The “Understanding” Email (The Mini-Proposal) Never leave a meeting with a verbal “yes.” A client’s expectations are impacted every time they perceive that a commitment is made. Immediately following any meeting where commitments are made, send an email that outlines the proposal. It must contain:
- Context: “Based on our discussion regarding [Issue]…”
- Deliverables: “I will deliver [Specific Asset] in [Specific Format].”
- Timeline: “You will receive this by [Date].”
- Out of Scope: “This analysis will NOT cover [X] or [Y].”
This email is your shield. If they don’t reply with corrections, that is your binding agreement.
3. The 30-Second Status Ambiguity breeds anxiety. Anxiety breeds micromanagement. You must provide frequent progress reports to the client.
Do not write long essays. Develop a “30-second response” consisting of three key points regarding the project status: Completed activities, Upcoming activities, and Risks/Blockers.
Send this proactively. If the stakeholder has to ask you “how is it going?”, you have already failed.
4. The “No” Pivot You must fiercely protect the ability of your teammates and clients to count on you. That means you cannot overcommit.
Avoid working until 2 a.m. by pushing back on unreasonable expectations. When a request comes in that breaks the scope, do not say “I can’t.” Say:
“To deliver [Original Promise] on time, I cannot add [New Request] right now. We can add [New Request] to the backlog for next week, or we can delay [Original Promise]. Which do you prefer?”
This puts the decision back on the stakeholder.
Final Thoughts
Meeting client expectations is the most fundamental principle of our work. But you cannot meet expectations that are invisible, shifting, or unrealistic.
By adopting this consulting mindset, you stop being a servant to the queue and start being a master of your time. You are defining the terms of your engagement. You are getting to the Ask Behind the Ask. You are ensuring professionalism.
Next week, we will move to the second phase: The Thinking. We will discuss why you need to stop exploring data aimlessly and start planning your thinking before you gather a single fact.
Until then, manage your scope.
Keep Analyzing!
