Building a data protocol to reveal the real story behind project failures
“what the original and where, you know, we end up, it's it's an evolution, but I I would say that the original version was all data.”
what the original and where, you know, we end up, it's it's an evolution, but I I would say that the original version was all data. There was no front end. The idea was, how do we collect the pieces of information without giving humans any extra work? Collect the pieces of information to sew together a tapestry of what the real story is. What is the real story of this project? Why did it cost this? Why did it fail? Why was it successful? Why was it delivered late? All of that information exists in so many different places, and the idea was to create, essentially, a protocol in order for that to happen. Now I can tell you once we get into it a little bit more how difficult that is. I was gonna say, like, and especially in 2018, like, that sounds very I mean, it sounds very valuable, but it sounds very hard. It was crazy.
About this clip
Briq's founder explains their original vision to automatically collect scattered project data without human input to understand why projects fail, succeed, or run late. He describes the ambitious goal of creating a protocol to weave together information from multiple sources into a complete project narrative. The founder acknowledges how technically challenging this data aggregation approach was, especially in 2018.
Why this clip
Shows the ambitious technical vision behind an early-stage product and the founder's honest reflection on its difficulty.
What they said next
The harsh reality behind industry promises of APIs and interoperability
5:11 - 31s · founder story
More from this episode
Similar clips from other shows
From the blog
Want clips like this for your podcast?
We find your top 5-8 clips, write the hooks, and deliver ready-to-post content. First 2 episodes are free.
Get 2 Episodes Clipped Free