Working together
How to work with me
A guide to how I think, collaborate, lead and make decisions.
On this page
- 01 First, how I see work
- 02 I don't need you to agree with me
- 03 PoC or die: ideas need evidence
- 04 I value autonomy and ownership
- 05 Intellectual conflict is healthy
- 06 There's a time to debate and a time to execute
- 07 How I see leadership
- 08 How I give and take feedback
- 09 Mistakes are part of the process
- 10 What you can expect from me
- 11 What I expect from you
- 12 One last thing
01
First, how I see work
I like hard problems. Above all the ones that need creativity, critical thinking, research and the ability to build a solution where no clear answer exists yet.
I think the best results show up when we put capable people together, give them autonomy and point them at problems worth solving.
I don't believe in working hard for its own sake. I believe in working smart, understanding the problem, and executing with resolve when that's what the moment asks for.
My philosophy is simple: we research, ask questions, form hypotheses, run PoCs, measure the results, learn and adapt.
02
I don't need you to agree with me
In fact, I hope you won't always agree.
I want to work with people who can question my decisions, argue with my reasoning and tell me when they think I'm wrong.
I don't read disagreement as disrespect. The opposite: when it's well founded, it's a contribution.
If you have a better idea than mine, I want to hear it. And if you can show it works better, I have no problem changing my mind.
What I don't like is arguing forever without moving toward a conclusion.
It doesn't matter whose idea it is. It matters which idea is best.
03
PoC or die: ideas need evidence
I like ambitious ideas, including the ones that look impossible at first.
But an interesting idea isn't necessarily a good solution.
If you propose something, try to bring arguments, numbers, experiments, a prototype or a proof of concept along with it.
We won't always have complete evidence. When we do not, we need to name our hypotheses, weigh the risks and decide what is worth testing.
If I question your proposal, it doesn't mean I'm questioning your ability. I'm probably trying to find the weak points before we find them in production.
Don't fall in love with the solution. Fall in love with the problem we're trying to solve.
04
I value autonomy and ownership
Micromanagement doesn't interest me.
I'd rather work with people who can take in a goal, build a plan, make decisions and move without constant instructions.
That doesn't mean you have to solve everything on your own.
Asking for help, saying you don't know something, or raising a risk early are all things I value.
What I expect is initiative, and ownership of the commitments you take on.
If something breaks, I want to understand what happened and how we fix it. I have no interest in a culture where people are afraid to admit mistakes.
Autonomy doesn't mean doing whatever you want. It means having judgment and owning your decisions.
05
Intellectual conflict is healthy
I like to debate. I can be intense, direct and demanding when we're working through something complex.
Don't read that intensity as personal by default.
I'll question assumptions, look for inconsistencies and put hard scenarios on the table. I expect you to do the same with me.
We can confront ideas without attacking people. And we can disagree deeply without becoming adversaries.
If the way I communicate makes you uncomfortable, I want you to tell me.
Ideas should be able to take a hit. People should feel safe proposing them.
06
There's a time to debate and a time to execute
I like exploring alternatives, arguing over strategy and understanding the risks before we decide.
But once we have enough information and we decide to move, I expect commitment to the execution.
We don't need unanimity for every decision.
We can disagree and still work together toward a shared goal.
That doesn't make decisions irreversible either. If new evidence shows up, we correct course.
We decide with judgment and execute with resolve.
07
How I see leadership
I don't think a title makes anyone a good leader.
Leadership gets built by delivering on goals, and by showing judgment, ownership, the ability to execute and respect for people.
If you're my manager
Give me the goal and the constraints, not the steps. If the steps are important, tell me why.
Invite me to think, and ask me uncomfortable questions. I value having the problem shown to me through questions that guide my own thinking.
Tell me the real priority when everything is urgent, and say plainly what success looks like and how it gets measured.
Let me learn, build and bring ideas to the table, even when the early ones aren't the best. I want to hear your feedback, and why you think an idea is a bad one, so I can learn how you see the problem. If you let me take part and own the problem, what I bring gets better every time. If you don't, I'll get bored and I'll want to leave.
If we're peers
I like working with peers, whatever their seniority.
I expect to learn from the people I work with, as much as I expect to teach them something.
No title is involved, so nothing I say wins an argument on its own. Neither does anything you say. We settle it with evidence and PoCs.
If I'm leading the team
I'll give you the goal, the constraints, the context I have and whatever I have already learned. Sometimes we'll be facing something new together, so don't expect me to have all the answers.
We're a team. We can hold different opinions and different ideas, argue them and validate them, but we have to be Data Driven. The most creative idea doesn't win, the one with the best metrics does.
If something about me doesn't work for you, tell me. I can be intense and hold strong opinions. If that makes you uncomfortable, I'd rather talk it through and adjust how I behave. I want to work with you, not push you away.
If you're starting out
My job is to offer direction, tools, opportunities and feedback. Growth also takes initiative and effort on your side.
Ask the obvious question. Nobody was born knowing this, and the people who look like they were are the ones who asked earlier.
I don't expect everyone to want to become a manager or a team lead. A deep technical career is just as valuable.
My goal is to fight beside you, learn from you, add to the team and help it grow.
08
How I give and take feedback
My feedback tends to be direct.
If I think an idea has problems, I'll probably tell you which ones, why they worry me, and what we would need to improve.
I'd rather have one uncomfortable, useful conversation than weeks of ambiguity.
But I can also be wrong.
If my read is off, show me. If I wasn't clear, ask me for clarity. And if my feedback wasn't fair, say so. I don't expect you to guess what I'm thinking, and I expect the same from you.
I also believe in recognising good results, smart initiative, and the effort that produces learning, even when an experiment ends up not working.
Feedback has to help someone improve, not prove who is superior.
09
Mistakes are part of the process
Especially when we're building something new.
A new project is, in many ways, a laboratory of hypotheses, experiments and mistakes.
We can't avoid being wrong. We can avoid repeating the same mistake forever.
When something fails, I want us to ask:
- Which hypothesis was wrong?
- What signals did we miss?
- What did we learn?
- What can we change so it doesn't happen again?
- Can we turn that lesson into technology, automation, or a better process?
Permanent heroics don't interest me.
I care about building systems that get more robust and less dependent on extraordinary intervention.
A crisis handled well should leave us better prepared for the next one.
10
What you can expect from me
I commit to:
- Standing up for the team, and owning my part when things get hard.
- Giving you autonomy and room to build your own solutions.
- Questioning your ideas with arguments, and accepting that you question mine.
- Sharing knowledge, context and judgment.
- Admitting when I'm wrong and correcting course.
- Being transparent about goals, risks and decisions.
- Helping you grow, if you're willing to put in the effort.
I won't always get it right. I can be intense, impatient, and too persistent about certain problems.
If that starts to hurt the team or the outcome, I need us to be able to talk about it.
I don't want a team that depends on me. I want a team that asks the right questions, regulates itself and finds the best solution to a problem.
11
What I expect from you
Curiosity, judgment, ownership, and a willingness to learn.
I want healthy competition. Challenge the proposals on the table, and bring your own.
I need you to care about doing your work well.
That you question a decision when you find a problem, admit a mistake when you make one, and own what you committed to.
That you don't confuse being busy with creating value.
That you understand collaborating doesn't mean always agreeing.
And that you have the intellectual humility to change your mind when the evidence calls for it.
I'd rather work with someone who admits what they don't know and goes to learn it, than with someone who needs to look like they have every answer.
12
One last thing
I think the best teams aren't the ones that never run into trouble.
They're the ones that build the trust, the judgment and the capability to get through it together.
I like hard challenges. I like building. I like competing. And I like working with people who can teach me things I don't know yet.
The point is to build something worthwhile, learn along the way, and develop a product that keeps getting more capable.
I don't expect you to do as I say. I expect us to think together, challenge each other, and build something neither of us could have built alone.