Something we see often in requirements management software is the use of hierarchical trees for presenting requirements. Hierarchical trees are cumbersome not only because you’re constantly collapsing and expanding ‘nodes’ to find what you need, but you have to keep track of where you are. Why are hierarchical views used so often?
In my last post, I talked about popdowns, and how they turned out to be a failed experiment. This time around I’m going to show off something that we got right: batch updating.
Most of the feedback we’ve received during the beta has to do with the interface. Some good, some … not so good. In this post, I’m going to talk about Samepage’s “popdowns”, which are no longer.
The SamePage Beta has been going on for a few weeks now and we’ve received some great feedback. Special thanks to Chris Murphy, Pat George, and Ryan McGeary for their thoughtful and abundant feedback.
I’m going to do a few separate posts, each one covering a specific instance of feedback and what we did to address what we thought was some very fine criticism. The intent is to give a little insight into how we approach UI design, feature/simplicity trade-offs, and our thought processes in general when it comes to building a product we want our customers to love using.
Last Thursday we launched SamePage, our hosted service that provides an easy, collaborative way to manage, evolve and track project requirements. Requirements are anything that needs to be done or adhered to in order for a project to be successful. We use SamePage internally to plan and track its own features, assign milestones or builds, set priorities and keep track of who is working on what.
Before SamePage, we looked at third-party requirements management software, but nothing hit the mark. Our disappointments included cumbersome user interfaces, feature bloat, and token support for collaboration. So we set out to build something that keeps things simple and does what most people want, most of the time. Along the way, we came up with a few elegant navigation and editing features.
Since the launch, we’ve received insightful suggestions, a few minor bug reports and welcome compliments. We look forward to more of everything!