Data diagnoses problems, design treats them

You want to diagnose with data and treat with design. Data is not a tool that's going to tell you what you should build.

You can never skip the ideation, the design, the user research, the customer interview, the experimentation step. And you should always balance it with actually innovating yourself in your product.

I think that smaller teams, especially folks that are ideating, when you haven't landed on what you're going to build yet, I think Trello's a great product for that. For pulling ideas, for prioritizing them, for tracking how we're progressing through discovery, I think Trello's really great for that. For things that have been decided and are ready to go and are really in the breakdown these tasks and assign it to people, then something like Jira is probably a better use case.