Wiki » History » Revision 1
Revision 1/8
| Next »
Steven (eSHIFT) Uggowitzer, 27 May 2022 01:09 PM
AoS Tooks Wiki¶
A wiki is an investment in your product¶
If you’re going to build something people love, you need a wiki that enables your product team to grow and execute to a high standard. Without centralized documentation, your team will become increasingly disorganized with high fluctuation in quality.
Even if you do have guides and principles, they may be scattered and inaccessible. That's basically the same as not having them at all.
Your team deserves a single resource for:
Teams, roles, squads and their tasks — a directory of who's responsible for what features and products, what teams they’re working with, and how they're solving big problems together.
A neatly organized table of past learnings from user feedback, customer interviews and projects, each tagged so they’re easy to find and turn into actionable product improvements.
A reference point for everything your team does, which can be used by new and existing team members — OKRs and goals, onboarding resources, dashboards of data from experiments and your core product-building philosophies.
A clearly organized wiki becomes your product's standard-bearer, holding together PMs fanned out across projects. It gives them a playbook.
Before, PMs wasted time searching for the right information to do their jobs. Now, they know it’s in the wiki: shared learnings, a standardized process, conversations with users, areas of ownership, goals, and more. A wiki might be the single most high-leverage resource for your product team because it’s the place where all your most important documents converge.
Notion makes it easy to create, update and maintain.
We expect all AoS Tools to abide by the above and have a decent internal WIKI.
If the AoS Tool also has to appear on some other public hosted site (line Github.com) the information on this site should be considered MASTER SOURCE information. It is to be populated and used as reference for any public materials, and never the other way around.
Updated by Steven (eSHIFT) Uggowitzer over 2 years ago · 1 revisions
Go to top