A past project focused on polished dashboards instead of answering the actual business question. Software alone just digitizes existing workflows and delivers no value. Build something that works in the real world first, or you'll end up stuck in a pilot that never scales.
It felt like too much polish, but not enough answer. There was a huge attention to how the data were presented, but in the end, there was little adherence to what the original business question was. This was the other point that you made me realize, well, I shouldn't go for another software, piece of software myself, but I should work more on making that piece of real-world data Usable, yes.
I always find myself saying, but the software doesn't have any value. The software is just workflows that have been digitized effectively. Where's the value? Before you can start building software, you have to deliver the value. What do you think would have happened if you'd carried on going down the software route and got the product to where you thought it needed to be and then brought that to market?
Worst-case scenario, a very nice former colleague getting me the opportunity to pitch this inside a big organization, maybe running a pilot, but it would have stopped there, I'm pretty sure.
How Marcello Patané Turned An Idea Into Paying Customers in the European Biotech Sector
Why you should interview people who rejected you (as well as your customers).
