The Six-Week Trap: Why Joachim Schreiner Won't Promise a Fast Fix

Ask Joachim Schreiner to fix a sales organisation in six weeks and he will turn the job down. Not because six weeks is too little time. Because the promise itself is the problem.

Schreiner is CRO at ATOSS Software. Before that he ran sales organisations at Symantec, BMC and Salesforce. On the Sales Transformers podcast, he was blunt about the offer most new revenue leaders accept without blinking: a fixed timeline, agreed before anyone has actually looked at the business. "I wouldn't hire myself if someone said, we need to have the change completed in six weeks," he said.

Most new CROs do the opposite of what Schreiner recommends. They arrive with a plan already built. They announce it in the first town hall. They put a date on the slide and start executing before they have finished listening to the people who will have to carry it out. It plays well in the room. It rarely survives contact with the actual sales floor.

Schreiner spends that early period doing almost nothing that looks like leadership from the outside. He listens. Widely, and for longer than most boards are comfortable with. Only once he understands what is actually happening, not what people want him to believe is happening, does he start building anything with the team. Then he tests it. Then he hands it over, so the people running it own it, rather than simply executing his idea of it.

It is tempting to call this a change management problem. It isn't. The plan itself is rarely the thing that fails. What fails is the order. Leaders who fix the sequence tend to keep their changes: listen first, build with people rather than for them, test before you commit. Leaders who skip straight to the announcement tend to watch those changes decay within a quarter, no matter how good the plan was on paper.

Schreiner has evidence for why the sequence matters, and some of it comes from his own mistakes. Early in his career, he wanted to be a manager for the title and the money. When someone on his team underperformed, his instinct was to remove the problem rather than solve it. "I was more like firing him instead of developing him," he admitted on the podcast. It took him time to realise that a manager's job is to use the resources of the company to make the company, and the people in it, successful. Not the other way round. That single shift, from managing for himself to managing for the team, is the one he says changed everything else that followed in his career.

That same instinct now shapes how he runs ATOSS's sales organisation day to day. A CRO who tries to personally solve every problem becomes the bottleneck the whole team waits on. "You better kill bottlenecks before they create a bigger problem," he said. His fix isn't heroics. It's a deliberate system. Empowered peers who own their own decisions. A chief of staff whose job is to make sure things that get agreed actually get followed through. The goal is an organisation that keeps working when he isn't in the room. That is the opposite of the hero CRO model most sales leaders default to under pressure, especially in the first ninety days, when looking busy feels safer than being useful.

It's a similar principle to what SGT calls the Ground stage of the G.E.A.R. framework: baseline the real state of the business honestly before you design anything on top of it. Schreiner arrived at the same conclusion from inside the job, not from a methodology, and that's exactly why it's worth listening to. Independent validation from someone living the problem carries more weight than any framework diagram.

Listening first is only half of it, though. The half most people miss is what happens after you've listened. Schreiner runs every function at ATOSS against exactly three goals. Hit the number. Build the best team, through hiring he describes with zero ambiguity: "If it's not a clear yes, it's a clear no." And unify the wider organisation around one shared story, which he calls One ATOSS. Nothing outside those three counts as a priority, however good it sounds in a strategy deck.

The three goals will conflict with each other in practice. Chasing the number eats into the time needed for careful hiring. Building the team properly can slow down the very number it's meant to protect. Schreiner sets an explicit hierarchy in advance, so nobody on his team has to guess which goal wins when two of them collide. Without that discipline, listening just produces a longer list of things to do. With it, listening produces a small number of things worth doing properly. That's closer to what SGT means by the Objectives stage of C.O.V.E.R.: fewer goals, sharper goals, agreed and defended in advance, rather than a strategy document nobody on the team can actually hold in their head.

Schreiner told Matt and Chris he believes the CRO role is the best job in the world. He also thinks it burns through people faster than almost any other seat in the business. It demands two things at once that rarely sit inside the same person. The instinct and passion of a seller. And the rigorous, data driven discipline of someone who treats the business like a system to be tuned, not a story to be told. Most people are naturally strong in one. Very few are strong in both, which is why so many CROs last eighteen months and burn out trying to compensate for the half they're missing.

That's the real reframe underneath everything he said on the episode. The new CRO's real job in the first ninety days isn't to prove they can move fast. It's to prove they can listen properly. Then have the discipline to say no to almost everything the listening turns up, and mean it, even when the board wants a bolder answer sooner. Most leaders can do one of those things. Very few can do both, in that order, without skipping the first one for the sake of looking decisive in front of the people paying them.