Building and Leading Technical Teams

Hiring for Consulting vs Operations Roles

Consulting and operations roles require different profiles, even in the same technical domain.

Dimension	Consulting Profile	Operations Profile
Communication	Strong written + verbal; comfort presenting to executives	Clear direction-giver; shop-floor communication
Work style	Self-directed; manages ambiguity; switches contexts rapidly	Disciplined; process-consistent; repetitive task ownership
Client orientation	Builds client relationships; comfortable being evaluated	Internal customer focus
Travel tolerance	High (3-4 days/week on-site)	Low; single-site or HQ-based
Learning pace	Rapid; new industry/client every 3-6 months	Deep expertise in one operation over years

Hiring trap: Promoting a great operations manager into a consulting role because they “know the subject.” Domain expertise is necessary but not sufficient — consulting requires a different skill set that may not transfer.

---

Onboarding: 30/60/90-Day Plan

Structured onboarding reduces the time to productive contribution and signals that the organization invests in its people.

Period	Focus	Milestones
First 30 days	Orientation and observation	Complete all firm training; shadow experienced consultant on 2 client engagements; build internal network
31-60 days	Supervised contribution	Own a defined work stream within a team engagement; first deliverable reviewed and submitted to client
61-90 days	Independent contribution	Lead a client work session; present to client independently; identify a process improvement in their own onboarding experience

The 30/60/90 plan sets expectations and creates accountability — for the hire AND the manager.

---

Team Models

Model	Structure	Best For
Pod (generalist)	Small teams of 3-4 with overlapping skills; each pod can run an engagement	Variety of client types; cross-training priority
Functional (specialist)	Separate teams by domain (network, automation, 3PL); assembled per engagement	Deep expertise assignments; complex specialized work
Hybrid	Generalist engagement managers draw on specialist resources	Scale; allows specialization without siloing

Consulting practice context: Most boutique firms start as pods (everyone does everything). Specialization emerges as the practice grows and specific service lines develop traction.

---

Delegation: Task vs Outcome

Task delegation: “Go build a pivot table showing throughput by shift.” Clear, executable, defined output.

Outcome delegation: “We need to understand where throughput losses are happening on second shift. Here’s the data — what do you find?” Provides context and goal, lets the person determine how to get there.

Effective leaders match delegation type to team member readiness:

Trust ladder:

1. Do it; report back — low autonomy; detailed instruction; frequent check-in
2. Do it; report when done — moderate autonomy; outcome clear; check-in at completion
3. Do it; tell me only if there’s a problem — high autonomy; trusted individual
4. Decide and implement; don’t necessarily tell me — full delegation; senior team member

Move people up the trust ladder as they demonstrate competence and judgment. Don’t stay at Level 1 forever — it signals distrust and kills engagement.

---

Performance Management for Consulting Teams

OKRs in consulting context:

• Objective: Deliver the DC network study for Client X with the quality standard we’ve established
• KR1: Complete current-state deliverable by May 15, received without revision requests
• KR2: EVM CPI ≥ 0.95 (within 5% of budget) at mid-engagement
• KR3: Client sponsor NPS ≥ 8 at engagement close

OKRs should be ambitious but achievable. If every OKR is always hit, they’re too easy.

Distinguish coaching from managing:

• Coaching: Help the person develop their own answers. “What options do you see?” “What’s preventing you?” “What would you do differently next time?” Builds capability.
• Managing: Direct the work. “Here’s what needs to happen; here’s how.” Efficient for time-sensitive situations; doesn’t build capability.

Use coaching when there is time and the mistake cost is recoverable. Use managing when speed matters or stakes are high.

---

Psychological Safety

Amy Edmondson’s research established that team psychological safety — the belief that one can speak up, challenge, or make mistakes without punishment — is the strongest predictor of team learning and performance.

Behaviors that build psychological safety:

• Admit uncertainty and mistakes at the leadership level (“I was wrong about that; here’s what I learned”)
• Invite dissent explicitly (“Who sees this differently?” “What’s the weakest part of this recommendation?”)
• Respond to bad news with curiosity, not punishment (“Help me understand what happened” vs “Why did you do that?”)
• Follow up on raised concerns — if someone flags a risk and it’s not addressed, they learn that raising risks is pointless

Signs of low psychological safety on a consulting team:

• Everyone agrees in meetings; dissent appears in side conversations
• Junior consultants don’t raise concerns until a problem is already visible to the client
• Team members don’t share partial work for feedback — only “finished” products
• Near-miss incidents (scope mistakes, deliverable errors) are not discussed or learned from

High-performing consulting teams perform post-mortems on both failures AND near-misses.