2026-05-24
#22 Build With Intention | Outcomes Over Tasks
Hello Reader This week at Kiinara, we agreed to change how we work. We upgraded our philosophy of work, and the team got behind it straight away. Here's the idea we agreed on, and what it's teaching us. IntentionWe often measure effort. If we worked hard all week, it felt like a good week. Someone hit a wall and ran out of time, we'd say, "No problem, next week." It felt kind. It felt like how a good team treats each other. But it was quietly costing us. Because when effort is the measure, the work drifts. Everyone is busy. Everyone is doing things. But the thing we actually needed to move forward would sit in the same place week after week, wrapped in good reasons. We fell into working hard with no moving target. And a team without a target doesn't fail loudly. It fails slowly. You don't notice until a month has gone by, and nobody can point to what actually changed. So we decided to fix it together. InsightWhat we landed on is simple. Five parts. Nothing clever. That was the point. 01. We plan before the week. Before the week starts, we write down what we're delivering. One page, agreed by all of us before Monday. 02. Outcomes, not tasks. This is the one that changed everything. We don't track tasks anymore. We commit to an outcome by the end of the week. How each person breaks it down is theirs to decide. But the measure is the outcome, not the hours. 03. We demo on Fridays. Every Friday, each of us shows our work to the team. Not a status update. A real demo. And we decide together, as a team, whether it's actually done. 04. We use each other's time well. Anyone can pull me in to sit and work through something. That goes both ways across the team. The rule we hold is simple. Ask for help early, and use it for the things that really need it. 05. We don't go silent. If something isn't moving, we say so. The one thing we agreed not to do is let each other work in silence and find out on Friday. Speaking up early isn't a weakness here. It's the job. Now, the part that took the most courage for us to agree on. We decided that an outcome we didn't hit is a miss, even when there's a good reason. That sounds harsh. It isn't. We worked out why together. When a team accepts reasons, reasons become currency. People start spending them. Every miss arrives with a story, and the stories are all true, and somehow nothing ships. When the outcome is the measure, something shifts in the room. We stopped managing our reasons and started managing our outcomes. We plan better. We ask each other for help sooner. We cut the work down to what actually matters. It didn't make us tense. It made us focused. And it pulled us closer, because we're all holding the same line now, including me. It's something we set for ourselves. ActionHere's what I want you to try this week, whether you lead a team or you're a team of one. Name one outcome for your week. Not a to-do list. One outcome that means the week actually moved you forward. Then, on Friday, ask yourself one honest question. Did the outcome happen? Not "did I work hard." Not "was I busy." Not "did I have good reasons." Did the thing happen, yes or no? If yes, you had a real week. If no, sit with that for a moment before you plan the next one. The discomfort is the lesson. I hope this gives you something to carry into the week ahead. Build well |
Every Sunday
Enjoyed this edition?
Subscribe to get the next one straight to your inbox ~ free, every Sunday.
Subscribe →
