01
Take it on, take all of it.
Take the mission, not just the task. When you have the
mission, you can't be blocked: you find opportunity, you find a
way, never a justification. You don't wait to be asked. The
team becomes your crew, and your drive pulls them along.
You create the flow.
In practice
We own the mission, and the whole landscape is home. We don't say "not mine." We say "what else can we bring?"
Not this
"It's not my area. Find someone who owns it and give me a task." That's asking for a task. We take the mission.
02
If users haven't seen it, it wasn't delivered.
Working hard is not the same as delivering. Code in a branch
nobody knows about, a feature that runs locally but never hit
production — that's work, not delivery. Delivered means: on
stage, tested by the team, pushed to prod, and users are
actually using it. Ship the first part early, get real
reactions, improve from there.
In practice
Part one on stage with team feedback → prod → users react → next part. That loop is delivery. Anything that stays in a branch isn't.
Not this
"I worked hard on this." If the team doesn't know where it is and users haven't seen it, the effort is invisible — and invisible is the same as zero.
03
Do what you love. Love what you do.
When the mission inspires you, every task does too.
We are changing the way people work and live. That's the bigger
story behind every task on the list, every idea on the
whiteboard, every line shipped. When that story moves you, you
don't have to summon enthusiasm for the next thing — it's
already there. Loving the work isn't a personality trait — it's
what happens when the mission and the person fit.
In practice
We are inventing the future. You can't wait to get your next idea into production and into the hands of real users.
Not this
Losing sight of why the next ticket exists. The bigger story is right there — bring it back into view and the energy follows.
04
Your opinion is only as strong as what you've shipped.
A title earns you nothing. The team listens to the person
whose decisions are strong and whose impact
does the talking. Deliver the shiny gems. The team will
notice, and they will follow.
In practice
Earn the right to have a strong opinion by being the person who already tried it, already shipped it, already knows.
Not this
Loud opinions without the track record. The room goes quiet for the person who has done the work — not the one who speaks first.
05
If it isn't drawn or written, the thinking hasn't happened yet.
Words in a meeting disappear, and worse — they hide unfinished
thinking. A document, a diagram, a schema is where the
work actually happens. While you draw the box, name the field, write
the paragraph — you find what was vague, what was missing, what
doesn't hold. By the time you share it, the hard conversation
has happened with yourself, on the page. That's how thinking
becomes material.
In practice
Articles, sketches, schemas, structure. Build the artifact first, share it second. The gaps surface while you build, not in the room.
Not this
Walking in with a few words and pushing. Raw words bend and get misread. They also skip the work — they hide the thinking that was never done.
06
Think. Build great. The agents do the rest.
Users don't see your code. They see what you built.
We are not backend engineers or frontend engineers. We are AI
engineers and architects. Our purpose is to design, invent, and
deliver solutions that make users happy — not to write
boilerplate. Nobody measures the hours spent in an editor.
The agent writes the code. You own the architecture, the
decisions, the quality, and the outcome. Build with agentic
tools at full speed. Invent. Create. That is the art.
In practice
Design the solution clearly, use the agent to build it, review what ships. Two days of clear thinking + agentic execution beats two weeks of manual coding.
Not this
"I don't trust agents, I'm writing it myself — almost done" said twice in two weeks. Distrust of tooling is not craftsmanship. It's a delivery risk.
07
One coffee = one small improvement. Every day.
Have a small moment when you have time and inspiration but no
obligation to use them — in the morning, in the evening, on the
weekend. Use it for one small thing: fix the rough edge that's
been bothering you, sketch a feature nobody asked for, write
down an idea so someone else can pick it up. A
small piece of art × 365 × a team — that's a huge impact.
In practice
"I built a new feature over coffee yesterday — look at this. Oh, and I fixed that noisy bug while I was at it." That's the energy. Small, self-started, shared.
Not this
"I have a lot of ideas but no time — someone should prioritise this for me." Nobody will. The coffee slot is self-assigned. Pick one thing, do it now, don't wait for permission.
08
What you mastered last year is half-obsolete now.
The stack changes every month. The models change every week.
Curiosity isn't a personality trait here — it's part of how we get there.
Spend an hour a week on something new. Bring one thing back: a
paper, a feature, an idea. Try it. Tell others.
In practice
"Have you seen that new agentic feature that dropped yesterday? I already wired it into our pipeline — come see how it works." Learn it, use it, show it.
Not this
"I work the same way I always have. No time to read, I have code to write. I'm smart enough." The field moves every week. Standing still is falling behind.
09
Speed wins. And when depth is needed, nobody is coming to do it for you.
While we debate and postpone, others ship and win. Most
decisions are reversible — make them, move, correct course.
The perfect moment rarely appears. But when a problem is
genuinely hard and complex, don't wait for someone else to
solve it. Go deep. Leaders operate at all levels: they write
the strategy and they dig into the detail when it matters.
In practice
Default to action. If the decision can be undone, make it now. If the problem is deep and unsolved, own it — that's leadership, not heroics.
Not this
Weeks of alignment meetings while the window closes. Or the opposite — skimming a hard problem because "someone else will handle the details."
10
Answers don't appear. They are earned.
Don't expect someone to walk in with the answer ready. Answers
are the result of hard work — research, analysis, failed
attempts, and time spent sitting with a hard problem. Finding
the solution is the work, not a step before the work. Sometimes
there is no one else in the room who knows. That means it's on
you to go find out.
In practice
When nobody has the answer, that's not a blocker — it's the assignment. Do the digging, bring back what you found, and the team moves forward.
Not this
Waiting for someone smarter to solve it. Nobody has all the answers. The person who finds them is the one who looked.
11
If you're shipping, ship above expectations.
When your work is "done," ask one more question: can I fix the
thing next to it? Document the gotcha I just learned? Polish the
rough edge before merge? Bring twice. Not half. Don't make
someone else ask you to do better.
In practice
"I took that task, found two more edge cases along the way and fixed them, then shipped one more thing while I was there. It's already live. Users love it."
Not this
"It's on my laptop, not ready yet, I can't show it — it's not perfect. Maybe sometime. Sorry, next time." That's ½×. Work that can't be seen doesn't exist.
12
Minimum lovable. Not minimum viable.
"Viable" means it doesn't crash. "Lovable" means a user wants to
tell others about it. We aim for lovable, even at small
scope — especially at small scope, because polish is cheapest
there. The empty state, the copy, the small touch of delight,
the 5% nobody asked for and everyone notices — that's the gap
between "it works" and "I love this."
In practice
"We shipped fewer features than planned — but every single one is polished, needed, and delightful. Users are asking for more." That's the goal: less scope, more love.
Not this
"We delivered what we delivered. Who cares if users can't use it — we followed the Jira ticket. The problem was described poorly, so I did it poorly. Thinking is not our job, we code what's described." Come on. Agents think more than that.
