Engineering, product, design and security are core to building AI-native products. We prefer small, tight-knit teams working in the same timezone and, when possible, the same physical space.
Synchronous time is useful when it compresses coordination. A good standup can unblock something in minutes, a good demo creates shared context across the company and a good planning session gets a team pointed in the same direction.
The goal is not fewer meetings at all costs. The goal is meetings that matter.
Standup
Every workstream or pod has a daily standup. Keep it short, roughly one minute per person.
Everyone answers three things:
- What did you do?
- What will you do?
- Where are you blocked?
We prefer doing this synchronously over replacing the conversation with a bot. The value is not collecting status updates. It is creating shared context and resolving blockers quickly.
Demo
Every Friday, or Thursday on a short week, we demo what we built. Each pod or workstream presents its objective and the results from the week.
Everyone on the team is expected to attend. The rest of the company has an open invite.
The point is to show working software, not report activity. Demo creates accountability, spreads context and gives everyone a regular view into how the product is changing.
Planning
Planning happens weekly after demo. Each pod works with product to decide what matters next.
The format is simple:
- Quick retro
- Set the objective for the week
- Break the objective into tasks
- Assign work
- Assign a bug owner and prioritize bugs
- Surface upcoming OOO
Planning should end with everyone knowing what we are trying to accomplish next and who owns what.
Roadmapping
We do not plan the product quarterly or annually. The world is moving too fast for that.
We set targets and rough product scope for roughly six weeks, then reorient weekly as we learn. Product owns that prioritization by synthesizing customer feedback, product data, founder vision, market signals, competitor information and other research into a view of what matters most now.
The roadmap is a direction, not a contract.
1:1s
We do not default to recurring 1:1s. Recurring meetings tax our future calendars, and once a meeting repeats forever two things tend to happen: important conversations get delayed until the meeting, and sometimes the meeting happens simply because it is on the calendar.
Neither is useful.
Feedback should be direct, kind, actionable and given as close to the event as possible. Decisions should happen when they need to happen, and concerns should not sit around waiting for next Tuesday at 2pm.
This does not mean managers spend less time with their teams. It means the relationship matters more than the ritual.
Our expectations are simple:
- The senior or manager owns the relationship. They are responsible for understanding the people they work with, helping them grow and surfacing the unknown unknowns they may not see themselves.
- The individual owns asking for what they need. Reach out when you need help, feedback, clarification or simply want to talk. The same applies when you have feedback, ideas or concerns.
- Any team member can ask for time. If a conversation needs to happen, schedule it and have it. Do not wait for a recurring calendar event.
- Persistent gaps get structure. When we identify something that needs sustained attention, we create a plan with milestones and scheduled check-ins. Those check-ins have a purpose and an end date.
The calendar should reflect how the team needs to work, not someone else's management playbook.