Hi ,
Teams often lose momentum for a reason that is easy to miss:
the work is not necessarily that hard, but the context around the work is scattered.
The task is in Jira.
The decision is in a doc.
The latest implementation details are on a branch.
The AI prompt that explains the intent is sitting in chat history somewhere.
Everything exists, but not in one place where the next person can pick it up and move forward without retracing steps.
That's what I'm calling the shared context problem.
I've seen teams try to solve it a few different ways:
- keep the context in the main repo, but then everyone has to know which branch has the latest version
- keep it in another repo, but then context changes need their own PRs and reviews
- leave it spread across tools and keep paying the cost during handoffs, reviews, and AI sessions
I wrote a short article about why this happens, why the usual fixes break down, and what a better workflow could look like when the work and its context stay together.
If that sounds familiar, you can read it here:
https://dev.to/imdone/your-team-doesnt-have-a-jira-problem-it-has-a-context-problem-4akd
If you want to see the product direction behind it:
Happy Building!
Jesse
0 comments