Published June 21, 2019
Tomorrow uses Trello in several ways, with different boards for each part of the business. The flexibility of Trello helps different teams use it the way that works best for them. As the product-lead at Tomorrow, I get to pull from our product roadmap and customer feedback and tee things up for engineering.
Rather than creating one big backlog of tasks for the week, we use Trello columns to organize how features map to Tomorrow’s business model. This gives every member of Tomorrow’s engineering team two things:
The columns on the “Tomorrow Dev” Trello board are organized like this, including a couple of real cards as examples.
Acquisition — These features might make people want to use Tomorrow for the first time.
Delight — These features make people happy when they experience Tomorrow.
Retention — These features increase how often people might use Tomorrow.
Revenue — These features might help Tomorrow make more money.
Churn —Without these features, some people might quit using Tomorrow.
Regressions — These features used to work, now they don’t.
Legal — These features help Tomorrow users make sound legal decisions.
When Tomorrow does its weekly planning, after our Friday demo day, our engineering-lead Rambo (if you get that chance to have someone named Rambo to lead your dev team, take it!) lets each member of his team pull a card from any of the columns and add it to next week’s planning.
If you are an engineer who is tired of being assigned tasks without understanding why they matter to the business or are having a hard time getting excited about what you’re building, try using Tomorrow’s Trello framework at your company, or join us — we’re hiring.
If you don’t already, your team should try using Trello.