Lead with ownership using a clear why, skill solicitation, and customization
A product manager kicked off a crunch project with a slide full of dates. Eyes glazed. She tried again. “Because our users lose an hour a week on this, and fixing it frees time for their actual work. Because we’ll learn the workflow we need for the next release. Because doing this right earns us trust.” The room shifted. People stopped checking phones.
She didn’t ask for generic volunteers. She ran skill solicitation. “Who’s great at quick user interviews?” Hands went up. “Who enjoys systems mapping?” More hands. She matched names to tasks they could own. Then she gave constraints and freedom: the outcome, the must‑have quality bars, the deadline, plus room to pick methods and small features if they could justify them. The team perked up at the chance to make choices.
Midway through, she offered a custom option. “If daily stand‑ups aren’t helping your pair, swap to two longer check‑ins as long as you post an end‑of‑day note.” People adjusted without losing sync. A week later, a developer sent a message at 10:42 p.m.: “I stayed late because this flow is mine and I want it clean.” The manager smiled, then reminded him to log the extra time for comp.
Leadership here wasn’t pep talks or micromanagement. It was a clear because, matching skills to tasks, and giving ownership room to breathe. The psychology is straightforward: reasons create buy‑in, building increases attachment (the Ikea effect), and customization converts compliance into commitment.
Define the human because for your next project and say it out loud, then ask for strengths instead of warm bodies—match people to work they can truly own. Set the outcome and guardrails, and offer one custom option for method or cadence so they can shape how they deliver. You’ll see energy rise because people built it. Try it in your next kickoff.
What You'll Achieve
Internally, feel confident leading without hovering. Externally, see faster progress, higher quality, and greater commitment as people own work that fits their strengths and choices.
Use because, then let them build
Start with a real because
Explain the mission in human terms tied to them, you, and us. “Because this saves customers an hour a week,” “Because it teaches us a new capability,” “Because it lifts our whole region.”
Solicit skills, not volunteers
Ask, “Who’s great at…?” or invite by name for known strengths. Match people to tasks they can own end‑to‑end.
Add Ikea effect intentionally
Let people choose methods or customize parts. Ownership increases when they build it their way within clear constraints.
Close with a custom option
Offer one way they can tweak scope, sequence, or tools so the work fits their style without losing standards.
Reflection Questions
- What is the real human because behind this project?
- Which tasks map to which teammate’s strengths?
- Where can I safely offer customization without losing standards?
- How will we honor extra effort without burning people out?
Personalization Tips
- Nonprofit drive: “Because this funds 400 meals next month,” then ask, “Who’s strong at outreach calls?” and let callers choose their script variants.
- Class project: Share the core problem, assign roles by strengths, and let pairs choose tools (Slides vs. Canva) as long as they deliver the rubric.
Captivate: The Science of Succeeding with People
Ready to Take Action?
Get the Mentorist app and turn insights like these into daily habits.