KEN HANSEN

In my mid twenties I had arrived: a degree from a good university, a job at a Fortune 500 company, married to my high school sweetheart, a family started. In reality I was drowning: missing deadlines I did not know existed, dozing off in meetings I did not remember attending, and sitting in my boss's office trying to explain why I was failing at things nobody had told me were mine. At 27, my doctors told me I had ADHD.

The diagnosis brought two things at once. Relief, because there was finally an explanation and it was not that I was lazy. And a word. Attention deficit. I was, officially, deficient. That word did a number on me for years.

THE DISCOVERY

Almost twenty years later, in 2012, I was running sales operations at a midsized tech company and administering their Salesforce org. I had spent two decades cobbling together systems to manage my own workload. A few worked. Most did not.

One afternoon my CTO asked whether I could build a kanban board. I looked him straight in the eye and said, "Yes I can." Then I walked back to my desk and Googled what a kanban board was.

What I found was not a productivity trend. It was a method invented by an engineer at Toyota who had no money, no warehouse space, and no room to fail. Taiichi Ohno's insight was that the way to get more done is not to push harder. It is to limit how much is in progress so that work can actually flow. Too much in the system creates a jam, the same way too many cars create traffic.

I tried it on my own life. Two pillars: see the work, limit the work. For the first time I had a system that was working with my brain instead of against it. It has saved my job more than once since. It also finally got my garage cleaned out, which honestly took longer.

THE PROBLEM WAS NEVER YOUR BRAIN. THE PROBLEM WAS THAT EVERY SYSTEM YOU WERE HANDED WAS BUILT FOR SOMEBODY ELSE'S.

WHY I DO THIS

I wrote Work in Progress, out in early 2027, because I wanted the book I needed back then, the one that explains why the method works instead of just telling you to try harder with a nicer planner. Understanding the why is what makes people stay with a system past the third week.

I run the KanbanVibe Focus Room because a book cannot ask you how your week went.

I am not a guru and I am not selling a morning routine. I am a Salesforce architect who has spent twenty years building systems for enterprises and thirty living with a brain that needed one. I have also worked with business leaders and with friends who have never been diagnosed with anything, and who run this system successfully. That is my favorite proof that none of this requires a label. It just requires a system built for how you actually work.