My Sunday Self Would Be Embarrassed Watching My Monday Self Work

"Hey Jarvis, add that to my backlog." I said that while making coffee on a Sunday. By the time the kettle boiled, three tasks were sitting in Notion. Done.

Monday morning at work, I spent 15 minutes manually creating one Jira ticket. Opening the form. Filling the description. Adding context, sprint, release, related work. All by hand.

My jaw tightened. Not because the work was hard - because I'd already proven it didn't need to exist.

How Does Someone Who's Not a Developer Build This?

I didn't watch a YouTube tutorial. I just got annoyed enough to think it through.

What pulls me out of what actually matters? What do I repeat constantly? What would I never miss if it just... happened automatically?

Voice command triggers an automation. Task lands in Notion. Meeting notes get captured. Done before I've finished what I'm doing.

One Sunday. That's the gap between what's possible and what most people are still putting up with.

The Frustration I Can't Shake

Here's what gets me. It's 4:30pm on a Thursday. A leader needs to know how a feature works before a stakeholder call. They message me. I stop what I'm doing, dig into the codebase, write up an explanation, send it back.

Then an engineer asks if something's a defect or expected functionality. Then business needs clarification before they can write an Epic. Then a downstream team is chasing context that should've been self-serve weeks ago.

Every one of those is a meeting I didn't need to be in. A message that pulled me out of focus. A question the system should've been able to answer.

Upwards of 10-20% of my day, gone. Not because the technology doesn't exist. Because the organisation hasn't unlocked it yet.

I'm a human API. And it's killing my productivity.

What I'd Build Tomorrow (If the Constraints Weren't There)

Give anyone in the business the ability to query the codebase through an LLM. A living document of how our products actually work right now - not the outdated Confluence page from eight months ago.

That one thing cascades. Business can triage incidents without waiting for devs. Engineers spend less time explaining. Epics get written with accurate context from the start. Feedback loops tighten.

I know the governance exists for real reasons. I'm not naive about that. But knowing what's possible and watching it stay locked behind approval queues - that tension doesn't go away.

So here's the mindset shift I've had to make: I can't control what the organisation unlocks. I can control how I talk about it, how I push the conversation, and where I focus energy inside the constraints I've got.

Not waiting for permission. Working the edges of what's possible.

The Question Worth Asking

What's the one thing blocking your team right now?

Not the big strategic thing. The daily thing. The question people ask you most often - that's your automation target.

If it's "how does this work?", the answer is self-service access to current state. If it's "how do I do this?", the answer is a documented, automated workflow.

Start with the question. Not the tool.

The people who figure out how to remove friction - inside constraints or outside them - are the ones who end up doing work that actually matters.

What's your bottleneck?