Category: Thought Leadership

Every consultant has experienced it. A client asks for advice, agrees with the recommendation, then slowly drifts back to what they were doing before, while still paying for advice they have decided not to use. Rarely is it because the strategy was wrong, but because execution requires something more challenging than a good plan. It requires accountability, commitment and focus. 

Over time, we’ve learned to recognize the signals early. The strategy isn’t usually the problem. Focus begins to drift, competing priorities take over, and teams gradually return to familiar ways of working. It is what happens when an organization has not yet decided that focus matters more than momentum. 

Early in a consulting career, the instinct is to soften the advice in the hope it will be easier to accept. We have felt that pull ourselves. But advice that’s easier to accept is often easier to ignore, delaying the very outcome the client hired us to achieve. 

What we do instead is name what we are seeing, directly, while there is still time to course correct. If a client is distracted by shiny object syndrome, has too many initiatives competing for the same hours, or has dropped the consistency we recommended, we say so. Anyone can tell a client what they want to hear. Our responsibility is to tell them what they need to hear. 

Sometimes that conversation is the turning point and reveals a harder answer: not every client is a fit for the way we work, and that is not a failure on either side. It is a mismatch between what an organization is ready to do and what the engagement requires. Better to know that early than discover it six months into a retainer. 

This is why a discovery call matters as much as the work that follows, because it’s what tells us whether trust can be built and if there’s someone inside the company championing it. 

We lead with generosity, but we’ve learned that generosity without boundaries isn’t sustainable. Protecting our time means preserving the capacity to say yes where we can make the greatest impact. When trust, commitment, and accountability are present from the beginning, difficult conversations become easier, better decisions follow, and meaningful change becomes possible. 

Few meaningful accomplishments happen alone. 

Behind every successful business, career milestone, breakthrough idea, or period of growth is usually a collection of people who challenged us, supported us, taught us, encouraged us, and occasionally told us what we needed to hear. 

That’s the value of partnership. 

At its best, partnership creates something neither person could achieve independently. 

It creates space for collaboration, where ideas become stronger through conversation rather than remaining isolated. The best ideas rarely arrive fully formed. They evolve through discussion, challenge, and the willingness to consider a different perspective. 

We believe that collaboration is one of our superpowers. When one of us presents an idea for a new program or approach to marketing ourselves, we’ve learned that a good partner doesn’t simply agree. Thoughtful questions arise and blind spots are identified. This approach leverages experience, insight, and perspective that help move ideas from possibility to action. When we brought our own brand strategist in to shape our website, we gave her the words we wanted to convey. She moved beyond translating them literally. She interpreted the intent behind them and came back with something stronger than what we asked for. That only happens when a partner is trusted to push back on the brief instead of just executing it. 

Partnerships create trust 

We’re talking about the kind of trust that allows for honest conversations, and it reflects one of our core values, candor. Candor makes constructive challenge safe and possible. And itenables confidence to bring forward ideas before they are fully formed, knowing they will be strengthened rather than dismissed. 

Some of the greatest growth happens in those moments. 

Whether through mentorship, coaching, collaboration, or shared experience, people often move further and faster when someone is willing to invest in their development. The best partners encourage independence and create confidence. They empower others to think bigger, make better decisions, and pursue opportunities they may not have considered on their own. 

At The Strategy Department, we’ve watched this distinction play out in something as small as how a client responds when a recommendation doesn’t fit what they originally asked for. The organizations that grow are the ones willing to sit with that discomfort long enough to ask why, rather than asking us to soften the advice until it fits the plan they already had. The strongest organizations aren’t necessarily the ones with the biggest budgets, the largest teams, or the most resources. They’re the ones willing to invite different perspectives into the conversation, curious enough to challenge their assumptions, and disciplined enough to focus on what matters most. 

The greatest value of partnership shows up less in the work itself than in what the work makes possible: ideas sharpened through collaboration, confidence built through trust, opportunities that emerge because someone opened a door you didn’t know was there. 

The best partnerships leave both people, and the organizations they serve, better than they were before. 

Organizations often bring in outside expertise to fill a gap in knowledge, capacity, or experience. There’s value in that, but we’ve learned the greatest value doesn’t come from what someone knows. It comes from how they think, communicate, and contribute when the pressure is on. 

At The Strategy Department, we don’t look for contractors who simply execute a scope of work. We look for partners who make the work better. There’s an important difference. 

We’ve experienced this first-hand across different client engagements. Both contractors were technically capable, and both delivered the work. But the experience, and ultimately the outcome, couldn’t have been more different. The distinction wasn’t expertise alone. It was how they communicated, managed expectations, and partnered with us throughout the engagement. 

One told us what we wanted to hear. The timeline was “fine,” right up until the deadline arrived and it was not. We asked for key deliverables in advance so we could review before the client saw a draft. That request went unmet, repeatedly, without acknowledgment. By the time we understood the real state of things, there was no room left to fix it quietly. 

Another, on different work, operated the opposite way. She managed our expectations before we had to ask. During crunch time, she sent the message, “Don’t worry, we’ve got this,” while we were occupied elsewhere, and it was accurate. We were free to focus on the client relationship instead of managing uncertainty about our own production. 

It would be easy to dismiss this as personality, that some people communicate better than others. We think that misses the point. Long before either of us ran a business, we learned the same lesson in corporate environments: communication and QA/QC determine whether a deliverable succeeds. Everything else depends on those holding steady underneath it. 

We value partners who do more than deliver against a scope of work. They challenge assumptions, bring a different perspective, and strengthen the thinking behind the work. Those conversations can create a little healthy friction, but that’s often where the best ideas emerge and the strongest outcomes are created. A communication gap costs far more than time. It diverts attention away from solving the problem and toward managing uncertainty. Every hour spent wondering whether someone is on track is an hour not spent improving the work. Over time, that uncertainty erodes trust, and trust is what allows teams to move with confidence. 

This requires something from us too: asking what others notice, not just what they deliver, and building with people rather than directing them, the same way we expect clients to build strategy with us instead of simply receiving it. 

The standard we hold for our partners has never been perfection. It’s whether they communicate openly, raise issues early, and approach every engagement as a true partnership. Those are the qualities that build trust and consistently lead to better outcomes. 

Our clients deserve a team that can focus entirely on them, not one quietly managing its own breakdowns in the background. That’s why we’re intentional about who we invite to the table.  We would rather work with a team where everyone in the room contributes expertise, not just output. It’s the better way to work, and the difference shows up both in the final outcome and how the team feels along the way. 

Some of the best work we do happens in rooms where the stakes are high and the internal team cannot ask the hard questions without creating friction. But we can—we are your strategic advantage. Not because we are external to the organization, but because we are embedded enough to understand what matters and confident enough to say it. 

That is what embedded strategy looks like in practice. Not a status update. Not a standing check-in. A partner who elbow-deep in the work with you, tracking the pipeline, watching the horizon, and advising on which opportunities are worth your best effort. 

What that work looks like in practice 

It can mean running a pursuit workshop before a major RFP, developing the win themes, reviewing competitive positioning, or presenting market research that influences how the organization sees its own opportunity. It can mean sitting in a strategy session and asking the question the room has been avoiding or has not thought to ask. It can mean showing up after a pursuit is lost and helping the team have an effective debrief, prepare for the next client conversation, and walk into the client interview with confidence. 

What we call it 

Advisor. Strategic partner. The language that feels most honest describes what we do and how we work: We embed, do the work alongside the team, and build toward the moment they can carry it forward without us. Embed, Solve, Advise, Step back. 

If you are looking for someone to help your organization grow, win better work, and show up more strategically, this is how we engage.

We use AI. We use it for research, for first drafts, for synthesizing large amounts of information quickly. We are not here to argue against it. 

What we want to be honest about is what it cannot do, because that gap is where the real work lives, and it is a gap that is not closing as fast as the word on the street around AI suggests. 

What using AI well looks like 

We fed a lead’s corporate website, annual reports, and growth strategies into a chat, then asked where the intersections were with what we offer. What would have taken hours of manual research came back in minutes. That is AI doing what it is designed to do well: pulling from a large volume of information and synthesizing patterns. 

But the reason that output was useful is that we knew enough about our own capabilities, and about what a credible intersection looks like to evaluate what came back. We were not copy-pasting and sending. We were using the output as a starting point for our own judgment. 

That is the distinction. AI is a capable research assistant and a strong first draft generator. It is not a strategist. Knowing how to ask the right questions, push back on the outputs, verify sources, and evaluate what is useful requires the expertise that the AI is drawing upon. The tool is only as good as the person directing it. 

What AI consistently cannot do 

It cannot read the room, by identifying micro-expressions and tone shifts in a workshop informing that a conversation needs to change direction. It cannot know that a client prefers to meet over coffee and will give you more in an informal setting than in a formal presentation. It cannot pick up on the political context in an organization, the history between two people in the room, or the thing that is not being said but is shaping every response. 

It cannot decide what to cut from a proposal when you are three pages over the limit and everything feels essential. It cannot make the judgment call about which win theme will resonate with a specific evaluator based on what is known about their priorities. It cannot run an interview, facilitate a workshop or strategy session, or build the trust that turns a client relationship into a long-term partnership. 

These are not soft things. They are the core of what makes strategy work. 

Where we recommend leaning in 

• Research and synthesis, where the volume of information is large and the question is clear 
• First drafts, where speed matters and the human review is thorough  
• Compliance checking on proposals, where the task is systematic and the output can be verified 
• Identifying gaps in a document against a checklist 
• Tasks that are structured, specific, and where the output will be evaluated by someone who knows what good looks like 

Where we counsel caution

• Any output that goes to a client without a thorough human review 
• Any strategic recommendation generated without the context that only comes from being in the engagement 
• Any use of AI that skips the step of asking: do I know enough about this topic to recognize when the output is wrong? 

That last question is the most important one. AI produces confident, well-formatted, plausible-sounding content on topics it does not fully understand. The only protection against that is expertise. You cannot outsource the expertise to the tool. 

We use AI as an assistant. It saves time. It makes our work faster. It is not a replacement for the judgment that makes the work worth doing.

Most Business Development teams spend more time producing a proposal than they spend developing the strategy behind it. That imbalance is where most losses occur. 

A pursuit workshop flips that ratio. It is a structured session, run well before the RFP drops, and designed to build your capture strategy when you still have time to act. Done well, it is one of the highest-return investments a BD team can make. 

Here is what it is, when to run it, and how to make it work. 

What a pursuit workshop is 

It is not a proposal kickoff meeting or planning session, those come later. It is a deliberate conversation about the opportunity, the client, and your organization’s ability to position before the formal procurement process begins. 

The goal is to surface what you know, name what you do not, build a strategy around both, and obtain  clarity around these questions: Why this opportunity? Why us? Why now? Why not someone else? 

If your team cannot answer those questions well in advance of the RFP, the proposal is going to struggle to answer them under deadline. 

When to run it 

The earlier the better. Ideally, six to 12 months or more before a major procurement. That window gives you room to act on what you learn build relationships you are missing, address gaps in your qualifications, identify the right teaming partner, and position your team with the client before the formal evaluation begins. 

For smaller or faster-moving opportunities, even two to four weeks of structured pre-positioning changes what goes into a submission. The discipline of the conversation is what matters, not the length. 

Who should be in the room 

The pursuit lead, the people who know the client best and the technical lead. Someone who can speak to your organization’s differentiators with honesty, including where you are strong and where you are reaching. And a facilitator who is not emotionally invested in the outcome. 

That last role matters more than it sounds. When teams facilitate their own pursuit workshops they tend to reinforce what they already believe. An outside perspective creates the conditions for a more honest conversation. 

The questions that do the work 

Do we have a relationship with this client? What do we know about this client’s real priorities, beyond what the RFP will say? Who makes the decision, and who influences it? What do they know about us? 

What is our win theme for this specific opportunity? Hint: It’s not a tagline. It is the one thing that makes us the right choice for this client on this project. If it could apply to any proposal, it is not a win theme. 

Where are we strong, and where are we reaching? What would a well-prepared competitor say about us? What do we need to address before the submission? 

What does a strong submission look like for this client? What will they remember after reading several proposals? 

What happens after the room 

The value of a pursuit workshop is not the conversation. It is what the conversation makes possible. A capture plan. Clear ownership of relationship-building activities before the RFP. A win theme that the entire proposal and project delivery team can articulate. A proposal that knows what it is trying to do from the first page. 

Proof in Action 

TSD was engaged by a construction contractor for a major design-build pursuit. We had six weeks until submission with two extensions. When we got started there was no established proposal process of this scale on their side. It was their first time working with us, and their first time sitting down before a proposal was written to develop win themes and review competitive positioning. That session, and the market research we brought into the room, shaped everything that followed. 

The organizations that win consistently do this work. The ones that keep losing are still starting with the template.

If a lost pursuit doesn’t change how the next one is approached, the loss was wasted. 

Most organizations move on too quickly. The next pursuit takes over, timelines compress, and the loss gets explained away, close scoring, a preferred competitor, a tough call. Maybe all of that is true. None of it changes what happens next.  

A structured debrief does. 

What a debrief is 

It is a structured conversation with the right people in the room, designed to extract specific, actionable intelligence from a pursuit that did not go your way. Not a post-mortem. Not a blame session. It has two parts: an internal debrief and, when possible a client debrief. Each serves a different purpose. Both matter. 

The internal debrief 

Run the debrief within two weeks of a loss, while the pursuit is still fresh. Focus the conversation on what will change future outcomes. 

• What did we know about this client before the RFP? What did we not know that, in hindsight, would have changed our approach? 
• What was our win theme? Could every person on the pursuit team articulate it the same way? If not, the proposal probably could not either. 
• What did the executive summary argue? Was it a specific case for selection, or a summary of our qualifications? 
• Where were we genuinely strong, and where were we reaching? Were we honest about that in the proposal, or did we glaze over the gaps? 
• What would we do differently in capture, six months before this pursuit opened?

That last question carries the most weight. The debrief is not about the proposal. It is about what changes before the next one begins. 

The client debrief 

Request it. Most organizations do not. Many evaluators will agree to a brief conversation, especially if the pursuit was competitive and the relationship was professional. 

When the opportunity is there, use it well. Do not defend or explain. Instead ask and listen.  

• What did the winning submission do that resonated?  
• What would have made the proposal stronger?  
• Was there anything in our approach that raised questions you could not answer? 

Even partial feedback is useful. A comment about stronger alignment with constraints signals that the proposal lacked specificity, regardless of how it was perceived internally. 

What changes as a result 

Organizations that improve win rates treat debriefs as a standard practice, not a response to major losses. 

Over time, the impact is visible: 

• Stronger intelligence gathered before the next RFP 
• More precise and credible win themes 
• Better discipline in go/no-go decisions 
• Executive summaries that argue clearly and directly 

None of this comes from a general intent to improve. It comes from specific insight, consistently applied. 

The debrief is where the loss becomes an asset. 

An RFP tells you what a client is asking for. Your relationships tell you what they need. 

The gap between the two is where most proposals either win or lose. 

Procurement language is written to be defensible, not revealing. The evaluation criteria reflect what can be scored, and not necessarily what will drive the decision. By the time a formal opportunity is published, the client already has a sense of who they are comfortable with, who they trust, and the type of partner they are looking for. The document codifies the process because the decision has been forming for longer. 

Relationship intelligence is the practice of understanding that context before the RFP is written. 

What it truly means to know your client 

It means understanding who makes the decision and who influences it. They are rarely the same and the influencers are often more accessible well before formal procurement begins. It means understanding the real challenge behind the stated scope. Every project tells a story. There is a reason this is happening now, why it hasn’t been resolved, a shift in leadership, and/or a growth trajectory that changed the requirements. When that context is understood, proposals are written very differently. 

It also means knowing the political context. Who championed this initiative? What has been tried before? What failed, and why? What is the client organization worried about that they did not putin writing? 

It means understanding the competitive landscape from the client’s perspective, not just your own. Which firms have they worked with? What has their experience been? Why and where are they looking for something different? 

How to gather the right information 

Show up before the procurement. Attend industry events, join client office hours, and engage in informal conversations across the organization. The goal isn’t to sell, it’s to listen and learn to understand. The same relationship-building that gives access to insight is what builds trust, and trust is what a capture strategy is ultimately building toward. 

Ask better questions in the meetings you are already having. Most BD conversations stay at the surface because the questions do. What keeps the client awake at night about this project? What would give them confidence in a partner six months into delivery? Those questions get to what matters. 

Pay attention to what the client pays attention to. What they publish, what they present. Understand what shows up consistently in industry conversations. Organizations signal their priorities constantly. Most competitors aren’t paying attention. 

What it changes 

When you have built genuine relationship intelligence before any RFPs, the proposal writes differently. The executive summary speaks to what the client truly cares about, not what the template calls for. The win theme is specific to this opportunity, not carried over from the last one. The team section explains why these specific people, for this specific project, and it lands because it’sgrounded in truth. 

The difference is visible early. Proposals built on real client intelligence read with clarity and intent. Those built from the RFP alone do not. Evaluators feel it, even if they can’t immediately name why.  

The intelligence is the strategy. Everything that follows, the workshop, the proposal, the interview and presentation, is execution. Start there. 

Workshops shouldn’t start with an agenda. They should start with a clear understanding of what the organization needs to resolve. 

The most effective sessions are anchored in leadership priorities, where clarity is missing, decisions are stalled, or alignment is at risk.  

Often, the issues are clear. Where to begin is not.  

Before we design anything, we focus there: what needs to move, what’s been avoided, and what success must look like beyond the room. And that starts with a small set of questions:  

The questions we ask 

What decision needs to be made, and who makes it? This one emerges faster than people anticipate given how unclear decision authority often is. Because without clear ownership, nothing resolves. 

What conversations have not happened yet? Every organization has them. The ones teams circle but never name directly. An effective and impactful workshop creates the conditions for those conversations to bring them forward, address them openly, and ensure every voice is part of the conversation. 

Who is most impacted by the outcome? When stakes are uneven, behavior follows. An impactful workshop accounts for that; bringing perspectives forward and aligning the group around a shared goal. It is about designing a process that does not inadvertently silence the people most invested in the outcome. If someone stands to lose ground based on what the group decides, they manage that risk. Better to know going in. 

Where are the tensions that will need to be named? They exist in every organization. What goes unspoken doesn’t disappear but shows up sideways. A facilitator who knows where the pressure points are can move toward them deliberately rather than stumble into them. 

What would success look like six weeks or six months from now? Not at the end of the session. Not in the summary document or implementation plan. But when momentum is tested and priorities compete. That is the real measure. Designing backward from there influences what gets prioritized in the room. 

Why this matters more than the agenda 

An agenda is a schedule and discovery is strategy. 

When pre-work is skipped, the first hours of a session are spent determining what should already be clear: what the group is trying to accomplish. That is an expensive and uncomfortable way to get oriented, especially when time is limited and decisions need to be made. 

The quality of the questions asked before the session determines the value created in the room. 

If you are preparing to lead or commission a workshop, the agenda can wait. Start with the questions. The answers inform the agenda. 

It’s true: your website is the first proposal you will ever write for a client who is deciding whether to invite you into a conversation. And, it’s provocative to think about it this way. 

Many websites are treated as a description of what a business does. However, that is not what an effective, hard-working website does. 

When an evaluator, a potential client, or a decision-maker lands on your site, they are trying to answer one question fast: is this the team worth serious consideration? If the answer is not clear within seconds, they leave. And they may not come back. 

The four things a hard-working website gets right 

It does four things well; it:  

1. Tells you immediately what the organization does and for whom  
2. Provides credibility through specific, recent evidence and subject matter expertise: case studies, project descriptions, client work that shows capability, and thought leadership 
3. Makes clear who their people are and why they are the right people to perform the work  
4. Gives the visitor a reason to take a next step through a call to action (CTA) 

Most websites do some of these things partially. Few do all of them well. The gaps are usually in the evidence: organizations that have done strong work but have not made the time to document it. Case studies that don’t exist or are dated. Testimonials have been collected without being published.  

We have seen firms with impressive track records that were not verifiable anywhere on their site, which means an evaluator who does not already know them has no way to build confidence. 

If a visitor lands on your site and cannot quickly find what you do and why you are credible, they leave. And they go somewhere else. A chaotic or underdeveloped website signals an organization that has not yet decided to take itself seriously. 

The thought leadership connection 

Your website is where the ecosystem comes together. A LinkedIn post creates awareness and drives curiosity. A thought leadership article, hosted on your site, converts that curiosity into credibility. A case study converts credibility into confidence. The post gets people in the door. The site is where the case gets made. 

This means the site must be doing its part. If someone reads a strong post, clicks through, and lands on a page that has not been updated in two years, the signal they receive is that the post was a one-off, not evidence of a consistent practice. The site reinforces what the content is building. 

The update problem 

Small and mid-sized organizations struggle here for a predictable and understandable reason: nobody owns it. The website gets built, goes live, and then quietly becomes obsolete. A team member updates it when they have time, which means it updates inconsistently and without strategic intent. 

The most practical approach we have seen is systematizing the content creation process so that updates happen as a byproduct of the work. The moment a project is won is the right time to create the foundation of the case study, using material already in hand from the proposal process. By the time the project closes, the case study is nearly written. That reusable content strengthens the website, the next proposal, and the firm’s credibility simultaneously. 

The hardest thing to get right 

Treating the website the same way you would treat any other channel: with intention, consistency, and a clear sense of what it needs to do. 

Organizations know the value of a strong proposal. They have seen what a polished, well-structured submission can do for a relationship. The website is that submission, running continuously, to every person who is deciding whether to invite you in. Investing in it is a business development strategy. 

Every potential client who researches you before reaching out is reading a document you have not updated in two years. That is the first impression you are making.