I started as an engineer. I studied computer engineering, and early in my career I worked as a systems engineer, including RF systems work at Motorola. Engineering teaches you a particular way of seeing. You learn to think in processes and systems. You learn that anything you build is a set of components, and that a machine is really a puzzle you assemble, piece by piece, until the parts work together.
I was good at the puzzle. Then I started leading people, and I found the one piece that does not behave like the others.
Leading people is not the same as running a project. A project is components coming together, which is its own kind of engineering. People are components too, in a sense, but they are the variable you cannot fully control, and they turn out to be the most important one. Everything I ever built as an engineer was built for people to use. And when you lead, it is people who carry the work through. You can have excellent systems and clean processes and still find that the human part is what determines whether any of it moves. That realization reorganized how I think about work.
It also changed the question I ask. Once you see that both the human and the machine matter, the question is no longer which one wins. It is what the right balance is for this particular piece of work. Sometimes the person carries most of the weight and the tool assists. Sometimes the machine carries the routine and the person holds the judgment. The mix is never the same twice. Every role and every process has its own equation, and getting that equation right is the actual work. Most organizations never write it down. They let it happen by default.
Years of running projects taught me something else about what you cannot force. One of my early project instructors said it plainly: on any project you are managing scope, time, and quality, and you can trade among them, but some things simply take the time they take. You cannot compress every timeline by adding people. Some outcomes keep their own clock. As an organization grows, time catches up with it, and there are things you have to prepare for rather than accelerate.
The pattern I kept seeing as I led was this. Organizations are full of execution. People are working hard, producing, shipping, closing tasks. But execution is not the same as direction, and very few people can see where the whole thing is actually going.
I used to teach my leaders with a picture of a submarine. Everyone has a compartment. Most of us stay in it and work, heads down, and never step into the hallway to see the rest of the vessel. Only the few who can see above the water know where the submarine is headed. That is how many organizations run. Enormous, capable execution inside every compartment, and a small number of people who can actually see the direction, if anyone can see it at all.
Execution does not set direction. Direction is a decision, and decisions are made by people, not machines. A machine can help you move faster. It cannot tell you where you should be going.
So the real problem is a gap. There is the direction you intended, and there is what your people are actually accumulating toward, day after day. When no one can see the whole submarine, those two drift apart. The organization is busy and moving, but moving toward what? And are you measuring the right thing to know?
I founded Human + Machine Works to close that gap.
I wanted to build a way to sit with executives and help them see the whole picture, or first help them describe it: how their people, processes, systems, governance, and tools actually come together. When leaders can see the whole, they start to notice how much of their execution is abundant but undirected, and where the real distance is between intention and activity. Then the work becomes practical. What is the right equation for each part? Which tools should measure progress, and are you using them? Where can technology take you from a small step to a larger one without losing the thread?
That is what I want to partner in: a deliberate way of working, where a leader can say what they are doing, how they are doing it, and why, and remain fully accountable for the systems, the processes, and the people carrying it out.
Machines execute. Humans decide. I have spent my career on both sides of that line, building the machines and then leading the people. Human + Machine Works exists because the organizations that do well in this next era will be the ones that design the relationship between the two on purpose, and can still answer, at any moment, who decided, why, and who is responsible.