No orientation
October 2019. I had just been hired as a full-time employee at Samsung.
A couple weeks into it, I got pulled into a big room where everybody was tossing out ideas. The organization was planning the national sales meeting for the upcoming new flagship launch, and leadership was already assuming the reps needed basic training. Remedial stuff. The kind of thing you give somebody who has never sold a phone before.
I had worked in a store. I knew what their job actually was.
So instead of keeping quiet and observing like a normal person two weeks into a job, I started pushing back. I told them flat out: these people know more about the product than you do. They know their customers. They know how to sell. What they need from us is the deep dive on the new hardware, not a remedial overview.
I had never built anything this big. The reps I would be training had been on the sales floor for years. They expected deep knowledge on the new devices. Most of my peers understood that. The people who didn’t get it were the leadership layers above us.
Over the next couple of months, we built a whole slate of sessions for the meeting. I was assigned as one of the leads on two of them. One was a deep dive on the new flagship features, giving the reps the technical knowledge they needed for the new hardware. The other was about how to sell and pitch those features to carrier store reps.
One had been kicking around in my head for a while. The other came together because somebody had to design it and I had an open block on the schedule.
Then January came. The rooms were set. The reps flew in. And we ran it.
The first one
The first session of the day was Battleship. Classic grid, two teams calling shots at each other, except every shot could be powered up if somebody on the firing team could answer a deep-dive question about the new flagship features. The idea was that the reps would learn the spec sheet the same way you unlock a sword in a video game. Answer a question, get an advantage. Use the advantage to sink the other team’s ships. Repeat until somebody wins.
The mechanics sounded clean on paper. Two things turned out to be the problem.
The first was the pre-training. I was setting up training rooms in another part of the building when the main stage presentations were happening, so I only heard about it secondhand. The main stage had run long. The deeper feature walkthroughs that the reps were supposed to have heard before the Battleship session got truncated. Marketing fluff took too much of the time. The product mechanics got squeezed.
The reps walked into my session having never heard the answers to the questions we had built the entire game around.
You can guess what happened next.
Nobody could answer anything. The powerups never unlocked. The grid stopped mattering because the powerup layer was the whole point. The room got visibly frustrated. People started looking around. People started muttering.
The second problem was the game itself. Everyone in that room had played Battleship before. But the version we built had so many rule changes that nobody could just play it. The room would say yes, we know how to play Battleship, and we had to say no, you don’t, here let us re-teach you. That’s a terrible way to start a training session.
We had fun building it. The people demoing it knew the rules. But the room had to spend more time learning the game than learning the content.
The session got a nickname that night. I can’t write it in a published post. But the room didn’t leave calling it “Battleship.”
The only option left
Working for Samsung had been a goal of mine for years. I sacrificed to get there. Moved my family hundreds of miles away from home to make it happen. So when Battleship went sideways, I really felt the pressure. This wasn’t just a bad training session. It was the job I’d worked years to get, and it was falling apart in front of me.
I didn’t have a great option. I had a room full of frustrated reps, a game that no longer worked, and a microphone in my hand. I could feel the energy turning.
So I stopped running the game. I told the room, plainly, that the earlier sessions hadn’t set them up to win at this one. I owned it. I didn’t blame the main stage. I didn’t blame the truncated walkthrough. I said, this is the situation, here is what we’re going to do instead, and I started walking the room.
I went table by table. I asked the questions out loud. When nobody had the answer, I gave it to them, and I let them ask follow-ups. I let them argue about which features mattered more. I let them compare what they had been hearing in their districts. I turned the session into the thing I had been trying to avoid in the first place: a conversation.
It wasn’t the session we’d designed. It wasn’t the session we’d wanted to run. But it was the session the room needed, and once I stopped trying to force the game and started filling the actual knowledge gaps, the frustration drained out. People started asking better questions. People started teaching each other. The room changed.
I walked out of there not knowing what to make of it. The session was a loss. The game was too complicated. The pre-training had fallen apart. The sessions were already built. The day wasn’t over.
The second one
The second session was mine. Well, ours. Demo Dojo was my brainchild, but I co-led it with another person who helped shape it into what it became.
The idea was simple on paper. I wanted to get people doing roleplay without ever calling it roleplay. Sales reps hear the word “roleplay” and their eyes glaze over. They have done it badly a thousand times. They know the awkward silence after the customer line. They know the manager standing in the corner with a clipboard.
So I didn’t call it roleplay. I called it a competition. Districts against districts. Each team picked a volunteer to step onto a mat in the middle of the room. We put a karate belt on them. They took turns pitching the new flagship to each other while the rest of the room watched. After each round, the decision-makers for each team, the DMs, had to huddle up and agree on who won the round.
That last rule is the one that mattered. The DMs had to come together and decide, out loud, in front of everyone, who had the better pitch. There was no judge. There was no app. There was no score. Just two people from competing teams having to look each other in the eye and say, okay, you got that one.
One of my former colleagues described Demo Dojo better than I ever could. “Player against player. You are going to demo the same thing. Someone is going to declare a winner. As soon as you hear the rules, as soon as you see the setup, you know exactly what to do.” That was the whole point. No learning curve. No manual. Just two people and a karate belt.
One thing I didn’t build into the design turned out to be the best part. Before the last round, the trainer running the session and I came up with a surprise. We had the district managers come up and compete against each other. We kept it secret until the moment. When the trainer said, “DMs, it’s your turn,” the room erupted. The reps were so engaged they were standing. The competition kicked into another gear.
One of the districts didn’t have their DM in the session, so I had to fill in. I went up against another DM and wiped the floor with her. The other team protested. “That’s not fair, you made the training.”
But it wasn’t that simple. Years before I joined full time, I worked as a contractor for Samsung as a SME inside AT&T call centers, learning how to influence carrier reps. I wrote about that in Seeing the Forest Despite the Trees.
The Samsung field sales reps do the same job. They’re influencers. Their job is to train carrier store reps, to sway them. The skill was never about device features. It was about how you present the information and whether you connect with the person in front of you. That was the whole point of Demo Dojo.
Demo Dojo is still talked about. I hear about it when I run into people from that era. It was only after running it that I understood what had gone wrong with Battleship. The contrast was right there. One was simple. One was complicated. One worked. One didn’t. The lesson from it is one I lean on constantly, and it’s the same lesson I should have remembered when we designed the first session.
The paper bag wins
Gamification for gamification’s sake is bad. Gamifying something more doesn’t make it better. Simple wins more often than not.
Battleship was overcomplicated. We built it because we thought the structure would carry the content. The grid would be fun. The powerups would be motivating. The competition would give the room a reason to care about deep-dive feature knowledge. None of that mattered, because the underlying knowledge wasn’t there and the rules were too many. The wrapper couldn’t save the gift.
Think of training like a gift. The training is the box and the wrapping paper. The actual content is the gift inside. If you put a pair of socks in an expensive box and wrap it in intricate paper with a perfect bow, you’ve set an expectation. The recipient opens it, and the expectation is subverted in the worst possible way. The wrapping doesn’t redeem the gift. It just makes the disappointment sharper.
Battleship was an expensive box with very intricate paper. Inside was a pair of socks. Demo Dojo was a paper bag with a bow drawn on it in marker. Inside was a karate belt and a reason to get loud in a room.
The paper bag is the better training.
I learned that in 2019. I’ve been unlearning it and relearning it ever since. The temptation to add more, to layer another mechanic, to build a more elaborate wrapper, never goes away. Every time I catch myself doing it, I think about a room full of frustrated reps who couldn’t answer a single powerup question because the main stage had decided their time was better spent on marketing fluff.
The answer is almost always simpler than the design we’re about to ship. The answer is almost always the version we almost cut because it felt too obvious.
Ship the obvious version. A paper bag beats an expensive box every time.