Four tools and no single view

The state of my team’s work lived in four places, and none of them showed the whole picture. Jira held the individual tasks. Confluence held the one-pager, the PRD and any technical documents that didn’t live alongside the code. Jira Atlas, meant to join it all up, held project updates for the executives. Nobody read it, so the real report became a PowerPoint, rebuilt by hand every week from the other three.

An hour a week, every week

I was CTO of a private equity-backed business at the time. Pulling the deck together took about an hour a week. Lose an hour once or twice and you shrug it off. Lose it every single week, to a job that exists only because your tools can’t give you one view of the work, and it drives you mad.

The hour wasn’t even the worst of it. With the detail spread across four levels of granularity, there was never a definitive version. The deck was the only place the pieces met, and it was stale by Monday. In a PE-backed company, where investors judge management partly on whether its reporting holds together, that is a credibility problem.

Integrations treat the symptom

We tried integrations to join the tools up, and migrations to cut the number down. Every attempt slipped. Each tool holds work at its own level: Jira has a task, Confluence has a page, Atlas has a project. Joining them means a translation from one level to the next, and it breaks the moment someone renames a status or reorganises an epic.

Reporting built for the meeting is theatre

The PowerPoint was what tipped me over the edge. A deck built for the meeting and rebuilt from scratch the following week is a performance, not a view of the work, and it always felt like theatre. A better template won’t help, because the problem isn’t the effort that goes into the deck. It’s that anyone needs to build one at all.

Transparency should be a by-product of doing the job, not a second job on Friday. That means one place that holds the work from the big idea down to the individual task, and every other view reading from it. Your CEO will never log into Jira. Send them a link that opens on the answer.

So I built the thing I wanted next time

I didn’t want to face this again, and rebuilding an internal tool is now within reach of one experienced person working with AI. So I built Slipdock, a kanban board with a wiki built in, where a big idea and every task beneath it sit in one tree and progress rolls up without anybody summarising it. Status updates go on the card they describe, and an executive gets a saved view they can open from a link.

Agents work from the same board. Anything I can do in the browser, an AI agent can do through its API, so an agent can pick up a card, do the work and leave its progress where everyone can see it.

You don’t need my tool to fix this. You need one place that holds the work at every level of detail, with every report reading from it rather than restating it. That might be a tool you already pay for, configured properly and used by everyone, or a reporting layer that pulls from your existing tools instead of someone retyping them. The tool matters far less than the rule.

Find the single view

This Friday, pick one feature and answer three questions about it from your tools alone: what’s done, what’s left, and when it lands. If one place gives you all three, you’re in better shape than most organisations I’ve worked with.

If the answer needs a slide deck, you haven’t got a view of your work. You’ve got a weekly reconstruction of it.