What does your team own?
Define the work, permissions and decisions that matter.
Built around responsibilities
Software that fits
the people doing
the work.
Start with what your team owns. Find the capabilities, controls and tradeoffs that make a toolkit useful.
Explore the guidesThink in capabilities
Before the shortlist,
understand the job.
Who needs to use it?
Choose for the people running the system, not just the feature list.
What can stay simple?
Keep the existing tools when another subscription would add more work.
Our first research guides are being prepared.
See how we evaluate software →