Articulating intent

Strengths

• Leads by example; actions create a powerful, authentic “north star”
• Avoids “communication bloat” and unnecessary corporate overhead
• Empowers high-context teams who prefer autonomy and minimal noise
• Efficient in stable environments where the “shorthand” is well-established

Liabilities

• Can leave team members feeling confused, unmoored, or “rudderless”
• High risk of misalignment on goals and specific performance standards
• New, remote, or diverse team members may struggle to “decode” the leader
• Subtle cues may be misinterpreted, leading to wasted effort

Development tips if you lean left

• Follow up a brief conversation with a 3-point summary of the core intent.
• Explicitly state the “Why” behind a new directive, even if it feels obvious to you.
• Ask team members to “reflect back” on what they believe the primary goal is.
• Create simple “Intent Documents” for projects to provide a baseline of info.
• Schedule regular alignment checks that are separate from status updates.
• Don’t assume silence means understanding; ask for verbal confirmation.
• Be more expressive with praise; “Implicit” leaders often forget to voice recognition.
• Use metaphors or stories to clarify abstract or long-term goals.

Strengths

• Ensures high levels of alignment and clarity across complex systems
• Effective at rallying people around a compelling “shared story”
• Reduces organisational anxiety by providing transparent, frequent updates
• Adapts messaging effectively for different audiences and technical levels

Liabilities

• Can overwhelm teams with “information overload” and meeting fatigue
• May be perceived as micromanaging or “over-explaining” the obvious
• Risk of a “say-do” gap if the articulated message isn’t backed by results
• Can stifle others by dominating the verbal and intellectual space

Development tips if you lean right

• Practice the “Rule of Three”: share only the 3 most vital points of intent.
• Pause and listen for twice as long as you speak during alignment sessions.
• Audit your messaging: could this 30-minute talk be a clear, 1-page visual?
• Ask, “What is the most concise way to frame this intent?” before speaking.
• Check if your actions are inadvertently contradicting your stated message.
• Give others the “floor” first to hear their interpretation of the goal.
• Use visual aids (charts/frameworks) to provide clarity without more words.
• Notice when your team looks “glazed over”—it’s a sign to stop talking and start doing.

If you lean toward implicit, you may:

• Assume that because you are doing it, others know why they should too
• Value brevity and “getting to the work” above all else
• Expect people to “pick things up” through proximity and observation
• Rarely repeat yourself, assuming once was enough for everyone

If you lean toward explicit, you may:

• Repeat key messages in multiple formats (verbal, written, visual)
• Spend significant time crafting the “narrative” or “story” of a project
• Provide detailed context and “intent” for every tactical decision
• Focus heavily on transparency and ensuring no one is “in the dark”

Articulating intent helps when:

• Managing remote or hybrid teams where nuance and context are lost
• Onboarding new staff who lack the historical context of the “inner circle”
• Leading through major organisational change, pivots, or uncertainty
• Aligning multiple departments with competing priorities and languages

Articulating intent hurts when:

• Too much deliberation and “framing” delays critical, split-second action
• Constant updates distract the team from the “deep work” required for results
• The “message” becomes more important than the actual mission outcomes
• Over-explaining makes a high-performing team feel patronised or mistrusted