Built by a leader who lived the problem.
I'm SSG Baddeley, an active duty Army NCO and the sole developer behind TroopToTask. I built it around the admin friction I've seen as a first-line leader, in the orderly room, deployed in the TOC, and as a Troop Clinic NCOIC.
The same friction, every assignment.
- Where:First-line leader The job:Squad and section What stuck:The same update, sent to five different places
- Where:Orderly room The job:Unit administration What stuck:Scattered trackers, unclear ownership
- Where:TOC · Deployed The job:Battle NCO What stuck:The idea surfaced. Missions came first. The idea
- Where:Troop clinic The job:NCOIC What stuck:Borrowed manpower, rotating every few months Built
In-processing, out-processing, clinic schedules, training calendars, access requirements, training records and competency packets all had to stay coordinated at once, by a small continuity staff already carrying patient care.
The clinic made the problem obvious, but it was not unique to the clinic. People move, requirements change, and leaders are left piecing the picture together from disconnected trackers. TroopToTask is the tool I kept wishing existed.
What stayed with me
“Never lose sight of the fact that every decision we make in these meetings is executed by a Soldier.”
TroopToTask is built for the leaders who have to make the plan work after the meeting ends.
One builder. Real users.
Not a defense contractor or a corporate team. One NCO, building close to the problem.
Leaders using TroopToTask across multiple Army locations decide what gets built next, what gets simplified, and what needs to work better.
- Is not An official Army system
- Is not A replacement for required systems of record
- Is not A government-endorsed product
- Is
A practical coordination layer for the work around those systems.
The handoffs, requirements, schedules, personnel changes and follow-through that leaders still have to manage.