The original is one click away. Open original ↗
Leadership Q&A: mission statements, networking, feedback, and bilingual teams
Executive overview
Leaders often conflate mission and vision, or write statements too complex to recall. A good mission statement uses plain language, answers the "why", and is short enough for anyone to remember without effort. Vision is future-oriented; mission is the present purpose.
This Q&A episode covers four listener questions with practical frameworks for each.
Mission vs vision: how to write a statement that works
- Mission (or purpose) = what your organisation is here to do today; the why behind your work
- Vision = where you're going; inherently future-oriented and always in tension with the present
- Use everyday language — if people need an exercise to memorise it, it's too complex
- Tap into the "why" (Start With Why, Simon Sinek, episode 223 is a reference starting point)
- Ask the people your mission serves what they think the organisation is here to do — their words belong in the statement
- A vision should always have tension (Senge's rubber band): no tension means the vision has collapsed into the status quo
- Start with your personal mission before leading a team through the exercise — authentic personal work makes group work more credible
- Anticipate cynicism: if past mission exercises went badly, share your own deep work first to rebuild trust
- Stories of impact ("I build cathedrals, not bricks") are more compelling than abstract purpose language
Remembering the right person at the right time
- A centralised contact system is the baseline — an app, CRM, or spreadsheet all work; the tool matters less than having one
- Hard commitments (follow up in six months) go into a task management system with a deferred due date so they're hidden until relevant
- LinkedIn works as a broad network log but doesn't suit deep, relationship-based networking
- Event-based networking suits people who connect better one-on-one than at surface-level gatherings
- Hosting curated events — pairing people who don't know they should know each other — is a high-value, low-pressure networking style
- When someone comes to mind at the wrong moment, capture it immediately (e.g. dictate to a watch, sync to task manager) rather than trusting memory
- A tiered contact list (e.g. 40–50 people, segmented by contact frequency: every two weeks / every few months / annually) is more actionable than an open-ended network
- CRM tools like Contactually automate reminders when you haven't contacted someone within a defined window
Asking for feedback without looking weak
- In most organisations, seeking feedback signals strength — but execution matters
- Asking without acting on feedback looks worse than not asking at all
- The credibility test: are you decisive and clear-cut in your other behaviours? Feedback-seeking reads as courageous when paired with confidence, not as compensating for indecision
- Decide in advance what you'll do with feedback before you go seeking it
- Act on one or two things per cycle and make the improvement visible — that's what earns investment and influence
- Sheila Heen's framework (episode 143) gives a six-step process for receiving, filtering, and acting on feedback
- Gender communication research (Deborah Tannen) notes that indirect phrasing ("we need to tackle this") can undercut the confidence signal — directness ("you need to tackle this") reads differently to senior observers
- A useful feedback prompt: "What's one thing I could do differently, or that's holding me back?"
Supporting a bilingual team's development
- Finding leadership books and podcasts in Spanish is harder than expected — crowdsource from your audience and community
- A practical bridge: play short podcast segments, pause, ask the team to identify the question asked, then predict the answer before continuing
- Prediction is an evidence-backed learning technique — it increases engagement compared to passive listening
- After each segment, allow a brief Spanish discussion to confirm comprehension before moving on
- Separating receptive skill (listening, understanding) from productive skill (speaking, responding) lets you scaffold the exercise in stages
- The bilingual trust-building story in this episode — learning each other's language, sponsoring English classes — is itself a model for creative problem-solving in leadership
More like this — when you're ready for early access.
Join the waitlist for a personal account and content recommendations based on what you're working on.
No spam. Unsubscribe at any time.
You're on the list. We'll be in touch before launch.