Okay, here’s something that used
ishu trehan
Okay, here’s something that used to take a surprising amount of time…
We didn’t build features.
We rebuilt context.
PM explains the feature.
Designer explains the flow.
Developer explains the limitation.
Then someone writes docs.
Then someone updates tickets.
Then someone asks the same thing again in Slack 2 days later.
Nothing was technically broken.
But everyone was translating information differently.
And honestly?
Most sprint delays weren’t caused by coding.
They were caused by context loss.
AI changed this workflow for me.
Now instead of rewriting requirements 5 times…
I feed the real product context directly into the workflow.
PRDs.
Figma.
API docs.
Database schema.
Existing components.
Business logic.
The AI sees the same system we see.
So now the flow looks more like:
Idea → Context → Working implementation
instead of:
Idea → Meeting → Notes → Ticket → Clarification → Rework → Patch
The biggest shift wasn’t faster coding.
It was removing the communication friction that engineering teams quietly accept as “normal.”
Developers still own architecture.
Designers still own UX.
PMs still own decisions.
But fewer things get lost between them now.
Curious if other teams are noticing the same shift?
Like this project
Posted May 10, 2026
Okay, here’s something that used to take a surprising amount of time… We didn’t build features. We rebuilt context. PM explains the feature. Designer explain...
Likes
0
Views
1
