William Shemin was born in 1896 to Russian Jewish immigrants in Bayonne, New Jersey. He worked as a forester before the war, and he enlisted in the Army in October 1917, as soon as he was old enough to serve. By June 1918, he was a sergeant in the 47th Infantry Regiment, 4th Division, on the banks of the Vesle River in France.

On August 7, 1918, near a village called Bazoches, his unit hit a wall of German machine-gun fire that pinned them down for three straight days.

On three separate occasions during that fight, Shemin left cover and crossed 150 yards of completely open ground, exposed the entire way to heavy machine-gun and rifle fire, to drag wounded men back to safety. Not once. THREE times. Each trip meant walking back into exactly the fire he'd just survived, because there were still others out there who needed his help.

When the Chain of Command Disappeared

By August 9, the platoon's officers and senior noncommissioned officers had all become casualties. Shemin was the highest-ranking man left standing. He took command, on the spot, of a unit he had no formal preparation to lead, under fire that had already taken out everyone above him.

Shemin was wounded that same day, badly enough that most accounts describe him refusing evacuation until every one of his men was safe. He was found unconscious the following day and taken to a field hospital, where he spent the next three months recovering from wounds that included a bullet lodged behind his ear.

The Medal That Took Ninety-Seven Years

Some of his own men wanted to nominate him for the Medal of Honor. It became clear, at the time, that Shemin's faith would be an obstacle to the process. In 1920, he received the Distinguished Service Cross, the nation's second-highest honor, and the matter was closed for nearly a century.

In 2015, the Medal of Honor was finally awarded to Shemin posthumously, ninety-seven years after the actions that earned it. Shemin himself reportedly said, long before any of that recognition arrived: "War is not about medals. I love my country, I love my men. That's all that counts."

It would be easy to file this away as a story about bravery under fire. But the part of Shemin's story that actually teaches something is the moment his duty changed with little warning. He didn't apply for command. He was simply the last one standing when the obligation presented itself. His rank was Sergeant, but his title was leader.

That's what duty actually is. Not a feeling. Not motivation. It's what you owe the people around you because of the position you're in, whether you asked for that position or not, and whether you feel ready for it or not.

The Leader Who Gets Clear on This Before It's Tested

Most leaders never think seriously about duty until the moment it's suddenly required of them, the same way Shemin never expected to be running a platoon on August 9th. That's exactly the wrong time to figure out what you actually owe the people counting on you.

We believe anything is possible with great leadership. But that belief only holds up if the leader has already gotten clear, in advance, on what the role actually obligates them to — not what they feel like doing that day, and not what's convenient given the circumstances.

Shemin didn't discover his sense of duty in the chaos on the Vesle River. He'd already decided, long before that day, what kind of man he was going to be if the moment ever asked.

You will likely never have to command a platoon under fire. But you might be handed a project nobody else will own, a hard conversation that's technically not in your job description, or a teammate who needs someone to step up. Duty shows up in exactly those unglamorous moments.

Marching Orders

If you want to get clear on what your own role actually owes the people around you, take the free 3-minute leadership assessment. Your mission starts here.