You own the outcome. You don’t own the people.

Half the supervision. None of the reporting lines.

Somewhere in the last three years your company took out a layer of management. The work that layer used to do didn’t leave with it. It landed on you: the person who knows the system, who everyone asks, who’s on the hook for the date.

So you run the project. You unblock people, you chase the handoffs, you notice who’s quietly stuck. You do most of what a manager does for the people on it, with none of the things a manager has — not the title, not the 1:1, not the review, not the standing to say this isn’t working and have it land as anything other than a peer complaining.

You have all of the responsibility for the outcome and none of the authority over the people producing it.

That isn’t a gap in you. It’s the design. Here’s the long version of why.

What goes wrong is almost never technical.

Ask a tech lead what sank the last quarter and you won’t hear about the architecture. You will hear about the handoff that slipped twice and nobody named. The teammate who stopped asking questions three weeks before they missed. The person on another team who did the hard part and never heard about it, and is now a little slower to help.

None of that’s on the board. It’s not a ticket. It lives in your head, alongside everything else, and you push on it exactly as hard as you can without a title to lean on — which is to say, not very, and later than you should.

The good tech leads are the ones having those conversations anyway. Not because they’re braver. Because they have a system for noticing, and words that work sideways.

What Ren puts in front of you.

Ren reads the work you’re already in — the Slack or Teams channels you connect, the meetings on your calendar — and hands you the conversation that’s due. Not a dashboard. Three or four things a week, each with a name on it.

• The words, at the right altitude. A thank-you and a “this slipped twice” are different conversations. Ren drafts the opening for each, and it never sends anything you didn’t choose to send.
• Follow-through. Ren comes back and asks whether it landed, which is the part everyone skips and the part that makes the first conversation count.
• A record across the project. Who did what, what got said, what got resolved. When the retro comes, you’re not reconstructing it from memory, and the people who carried it get seen.

The Dial works without the title.

Under the hood is the Accountability Dial™, the five-stage framework from Good Authority that 100,000+ people have been trained on. It was written for managers, which is exactly why it’s useful to you: its first three stages — Mention, Invitation, Conversation — need no authority at all. A Mention is a sentence a peer can say. Most of what Ren surfaces resolves right there, in under a minute, and a good share of it’s praise.

The later stages are for when things are actually stuck, and Ren will tell you when you’re there. But it won’t pretend you can set a Boundary for someone who doesn’t report to you. What it will do is help you say the true thing early enough that you never need to.

Tell me the truth, but do it kindly. Give me a chance to reflect. Let me find my own way to the solution.

What it won’t do.

• Manage anyone for you. Ren has no opinion about who’s a good engineer. It notices conversations, not performance.
• Report on anyone. Nothing Ren shows you goes to their manager, or to yours. It reads the channels you connect, and what it reads is for you.
• Become another thing to fill out. There is no form. Nobody else on the project needs an account for it to work for you. When they want one, they can start the same way.