The hottest Management Substack posts right now

In New York City, car horns are used for many reasons, not just to express annoyance. They help communicate traffic situations quickly.
Drivers in NYC often resolve conflicts fast by using their horns, while in other places, politeness can slow things down.
Creating clear ways to share information, like dashboards, can help teams work better together and solve issues faster.

New York drivers regularly use their horns to communicate, not just to express annoyance. This shows how important clear signaling can be in resolving conflicts quickly.
In busy cities, being direct and loud can help traffic move more smoothly, unlike places with more reserved communication styles.
Using tools that share information quickly, like dashboards, can help teams be more transparent about issues and improve decision-making.

There's a new chat space for subscribers called The Engineering Manager subscriber chat. It's a place where you can talk and connect with others who follow the same interest.
In this chat, the host will share questions and updates for everyone to discuss. It’s like being part of a group conversation or a live hangout.
You can try it out for free for 7 days if you subscribe. This gives you access to all posts and updates related to the chat.

Listening to others and trying to understand their views first can help reduce arguments and improve communication.
Asking clear questions helps clarify discussions and keeps everyone focused on the main point without going off track.
Challenging ideas with thoughtful questions can lead to better decisions and a clearer understanding of goals.

Small details and subtle signals can change meaning and outcomes. Building reflexes to notice and fix those small errors pays big dividends.
Watch for three common thinking errors: assuming others' motives without asking, ruling out options too quickly, and deferring to authority. When you spot them, ask direct questions, explore alternatives, and choose what actually fits your situation.
Train simple habits like pausing, interrupting to check assumptions, and coaching people to self-correct. Those habits make teams catch and fix cognitive mistakes quickly.

Get a weekly roundup of the best Substack posts, by hacker news affinity:

Short, catchy phrases repeated often stick in people’s heads and change how they act.
Repeating the same message across channels and meetings turns it into an internalized habit—keep at it until people start begging you to stop.
Repetition is a powerful influence tool that can be used for good or ill, so use it intentionally and ethically to reinforce important behaviors.

Big changes can happen very fast when teams focus and use tight feedback cycles, with many goals reached in under three months and sometimes in weeks.
Your mindset matters: believing you can learn and change quickly makes rapid transformation possible.
Repeatable methods, lots of practice, and client commitment—like daily check-ins, genuine questions, and doing the hard homework—make fast, reliable results happen.

Real, specific external threats or immovable deadlines motivate teams more effectively than made-up goals because they create meaningful consequences people want to avoid.
Put responsibility in small, cross-functional teams with one engaged leader so work can’t be passed around and accountability rests where the results happen.
Make progress highly visible with frequent demos and scorecards so the importance is reinforced, rapid corrections are possible, and public accountability (within a safe culture) drives delivery.

Keep asking 'Why' until you reach root causes so you can be sure work actually serves the outcomes you care about, like profitability.
Playing the 'Why Game' with engineers is a quick way to check whether daily tasks map to strategic goals and to expose gaps between the kanban board and real business value.
Relentless 'Why' creates double-loop learning that turns failures into systemic fixes by revealing cultural problems, but it should be asked thoughtfully to avoid defensiveness.

You don’t need to be a technical expert to find, screen, and hire outstanding engineers; non-technical leaders can successfully run the hiring process.
There are practical, repeatable evaluation methods and interview techniques that let non‑experts assess candidates reliably and consistently.
Actionable guides and resources are available that provide step‑by‑step tactics, templates, and tests you can use immediately to build a strong tech hiring process.

Companies are shifting toward platform-style products where customers compose features from core primitives, which reduces the number of people needed to build and support those features. This is a strategic architectural change, not just a short-term cost cut.
Many recent layoffs are as much a correction for pandemic-era overhiring as they are about intelligence tools, and AI is often used as a convenient narrative; the quieter impact shows up as unfilled requisitions and paused hires rather than dramatic firings.
Engineers can’t just “build” and expect success — competition is fiercer and the moat is now distribution, trust, and business skills, so actively learning adjacent skills, experimenting, and adapting is wiser than staying passive.