Recently we have found ourselves using Trello more and more to manage our development tasks. The idea of creating User Stories to explain what features are needed rather than going into specifics about where this and that button should go has helped us all gain a common understanding of client and user goals.

Learn your lines

When creating stories, we follow this simple rule for creating our stories.

“As a user … , I want to … , So that…”

The value of asking ourselves this question first means different methods of achieving the common goal are suggested when group discussions are held. These can lead to prototypes being created such as wireframes which outline several potential routes and UI layouts.

Format your board

When creating our board with Trello, we create columns for deliverable dates and name our user story cards with simply what the card includes.

Within the card there is more information including our statement about what the user wants to achieve.

As we collaborate to design UI mockups, assign members to cards and add due dates, this is where Trello’s features really come into play.

We then can write the limitations of the system before the “Acceptance Criteria” is stated.

The acceptance criteria is what we need the system to do as a result of our ideation and collaboration phase to try to meet the user’s needs.

Our developers can pick up the cards and clearly view the requirements and implement the agreed changes before moving the whole card into a “completed column”.


User stories and Trello have gone hand in hand for our development process. It has helped us arrive at more logical and integrated solutions as well as collaborate our team.