Product complexity isn’t about features.
by•
Product complexity It’s about:
1-how many assumptions are embedded in decisions
2-how hard it is to trace why something exists
3-how many systems each change quietly affects
In AI-era products, this gets amplified because decisions are no longer just human-to-system, but system-to-system.
At that point, shipping isn’t the problem, understanding is.
Where do you think we’ll see the shift first, in planning, in release, or in development?
37 views
Replies
Athena
I think we’ll see the shift first in planning.
That’s where hidden assumptions accumulate quietly, before anything is built or released. Once those assumptions are baked into plans, everything downstream (development and release) just inherits the confusion.
Who doesn’t agree with me?
Athena
@maya_elor Completely agree.
Planning is where ambiguity gets compressed into decisions, and with AI in the loop, a lot of those assumptions don’t stay visible.
Athena
@luo_he
Yeah, I’m with you on this.
Feels like the real challenge is making AI-driven planning decisions legible.
Do you think tooling can solve that, or is this more of a process shift?