I should have been clearer about the specific problems I'm tackling. I’ll try addressing your points.
> On domain expertise
I've been in the trenches for over a decade since falling in love with Gantt charts, getting my CAPM certificate, and graduating college. First as a project manager on multi-year, $XX–XXX M projects, then as a self-taught SWE building PM software (we IPO'd a few years back). My domain knowledge is in oil & gas, construction, supply chain optimization, and manufacturing to a lesser degree. The scheduling tools I know best are MSP and Primavera P6.
> On the existing landscape
I agree that this is a well-established field of study. I'm using Google or-tools and evaluated a few other constraint solvers. However, I believe the focus has been more theoretical because actual software and tooling that people use day-to-day lacks any collaborative execution and management automation. In my opinion, this is where and why projects always break down.
* This leads me to the specific problem which I should have shared earlier! *
Every non-software rollout I was part of ran late and over budget. There's a stat that 90%+ of projects miss their targets. By contrast, agile software teams shipping sprint-sized features almost never slipped. The difference? Real-time collaboration and adaptability. (And yes, I'm aware the scopes are radically different!)
The moment we move from "just" the world of bits to the world of steel, gas pipelines, trains, and dealing with hundreds or thousands of people, equipment, 3rd parties... even the best plans crumble.
> Real world experience
I could go into minute detail on each one, but I'll spare you the reading and myself the PTSD by condensing a few pain points:
- No shared, real-time view. Data lived “somewhere,” but never with field teams or execs.
- Black-box auto-levelers (like Primavera P6) only delay tasks they don’t split or reallocate crews without the PM doing a ton of work. Small hiccups can easily compound into slips that last days or even months. Licenses are expensive and access is gated so only “the scheduling team” sees the live plan. I’d argue it’s not a solved problem otherwise we would not have needed to also bring on dedicated scheduling consultants.
- Process workshops and Excel jockeying can’t keep pace with real-world churn. Any good plan evaporates once work actually starts. We did these things on every project but I don’t think it really made a difference because while people are a variable, bad tooling is exponential.
> My approach
Rather than building another optimization engine, I’m creating a collaborative platform where scheduling is a core feature. Most tools focus on the initial optimization but ignore the continuous re-planning that real projects require. Not everyone _needs_ the schedule obviously, but the schedule _definitely_ drives the project. I want to enable realtime ADAPTATION as conditions/constraints change in the field.
I’m particularly interested in connecting with others who’ve hit similar walls, or who have insights on bringing real-time collaboration to complex, distributed projects so I really appreciate your response.