I like this idea! 💡 Never tried a one apger proposal before or see anyone do it. It actually make sense for most cases. But I think some projects are just too big and detailed to summarize in one page.
But I get it the more concise and clear the ideas are and the less the jargons and unimportant things attached the better traction the proposal will get.
Nothing is too big to be summarised in one page. 😀
The constraint forces you to really focus on what matters and remove the fluff.
BTW pretty much everything Amazon has built began life as a one-pager, if their huge projects like AWS can begin that way, the rest of us can probably manage it too.
It is actually an interesting idea to think about. I wonder how in the company I work for they can accommodate this. For example, they do architecture review tht requires staff engineers to review the proposal and who are not in the same team and are not necessarily involved in the systems we own. So they need a little bit of context, background and details. But I think most of the time they feel lost in the details also 😅
I'm not surprised, you're a smart guy Jordan. I heard of the idea of brevity from Kevlin Henney, but it never clicked until I read about it's use at Amazon.
It’s a great practice though. I tend to write long confluence documents, which is often useful as it has more information, but it doesn’t serve the purpose of conveying the essential message.
I like this idea! 💡 Never tried a one apger proposal before or see anyone do it. It actually make sense for most cases. But I think some projects are just too big and detailed to summarize in one page.
But I get it the more concise and clear the ideas are and the less the jargons and unimportant things attached the better traction the proposal will get.
Thank you for this great advice!
Nothing is too big to be summarised in one page. 😀
The constraint forces you to really focus on what matters and remove the fluff.
BTW pretty much everything Amazon has built began life as a one-pager, if their huge projects like AWS can begin that way, the rest of us can probably manage it too.
It is actually an interesting idea to think about. I wonder how in the company I work for they can accommodate this. For example, they do architecture review tht requires staff engineers to review the proposal and who are not in the same team and are not necessarily involved in the systems we own. So they need a little bit of context, background and details. But I think most of the time they feel lost in the details also 😅
I've just introduced it in the company I've joined. We do a one pager to introduce the idea and get buy-in for it to progress.
We do a longer version for the final decision that acts as the final review and ADR.
FYI Amazon apparently does something similar with 1 and 6 page version.
Thanks for the solid one-pager template, John.
This is also one of those things I accidentally did without realizing it earlier on in my career and it was a game-changer
I'm not surprised, you're a smart guy Jordan. I heard of the idea of brevity from Kevlin Henney, but it never clicked until I read about it's use at Amazon.
The tough part is to make everyone read it 🙃
It’s a great practice though. I tend to write long confluence documents, which is often useful as it has more information, but it doesn’t serve the purpose of conveying the essential message.
True, it's often tough to get people to read them, but one page is easier than many pages. Small wins 😀
saying more in less words it's great practice for developing awesome writing skills :)
Isn't it and one I think you're a master of.