I thought to send this based on our earlier conversation about sharing updates to stay aligned.
Over the past 2 to 3 weeks, a lot has been coming at the team.
This level of demand is honestly a good sign. It means people are beginning to trust Seamless and want their work sitting on it. And it's across the company now, not from a policy level but genuine interest. But all of that together is pulling the team in too many directions at once.
And honestly, my team and I haven't done the best job of keeping an updated roadmap out there that shows everyone where their requests come in. So I felt it was wise to step back and sequence everything into one plan. You'll find it at the end of this letter.
The plan runs in what I've called "focus waves". In each wave, we commit to a group of things across all five areas (open for conversation).
We've tried something like this before, from Nairobi. But then, we as the AI team optimized for engineering and shipping new features every week. This time, every wave requires that everything listed in the wave is engineered and adopted. Building is kind of the cheap part now, quality control and adoption are where the real effort goes. That's sitting with the users, making tweaks, refining, fixing bugs. I'm sure you've probably gotten a taste of this with the Treasury agents and the Brain (LOOOOOL). We're getting them not just to adopt, but to take ownership.
The rule I'm thinking will make this work: waves ahead of us stay open and can be reshaped any time. But once a wave starts, it's locked. New requests go into a future wave, whether the next one or a later one. Everything still gets done, just in order, without breaking focus midway.
Ideally, this would flow from the strategy work, but that hasn't kicked off yet. This can keep us moving. It's built to align, and if strategy ends up moving in a different direction from what we have, we'll just adjust the waves to follow it.
Look through the plan, particularly Wave 1, which I want to run from this coming Monday through July 26. Then let's take 15 to 30 minutes to talk it through and get your go-ahead. You can also send me a letter back if anything feels like it belongs in a different wave, or something should be in Wave 1 that isn't, and we swap it before Monday.
Pelumi will be joining and driving the wave-planning conversation each cycle. She's in with every team, speaks with them constantly, and has the most context on adoption, so she can keep us all aligned on what goes into each next wave.
Would love to chat once you've read through.
Obose