Why I Built the Roundtable

Fifteen years ago I started sitting across from people who came to me for advice. Owners. Families. Pastors. Founders. People trying to buy their first home, people trying to save a business, people trying to figure out what to do with money they were scared to touch.

Early on I thought my job was to give them information. So I got good at credit, lending, banking relationships, and capital sequencing.

The people sitting across from me usually already had the information. Sometimes they had more information than I did. They had the numbers. They had the options. Some of them had spreadsheets, advisors, attorneys — whole tables full of smart people.

And they still couldn't move.

It wasn't that they didn't know enough. They didn't know which step was theirs. The goal was clear; the next step was buried. The more voices they collected, the more buried it became.

I watched it in a grandmother trying to buy her first house in Milwaukee, in a pastor carrying responsibility for a congregation, and in business owners who could run a crew of forty but froze in front of a contract.

The moment the instrument was born wasn't a big moment. It was just the day I finally admitted the pattern was the same everywhere, and that more information was never going to fix it.

When people come for counsel, they often ask for answers. I learned to slow the moment down instead — to separate the decision from the fear, the ego, and the pressure of whoever is watching.

Over the years I have taught financial principles to more than fifty pastors — some sitting across from me one at a time, some in groups I have led. I ran workshops for the City of Milwaukee and nonprofits on credit and banking relationships. I helped thousands of families in my hometown get into their first homes — not by handing them money, but by teaching, by giving them understanding, by clearing the confusion that was stopping them from moving.

The same difficulty kept appearing: the numbers were present, but the next step was buried. Status did not remove that difficulty. Sometimes it only made the consequences larger.

Here's the part that took me the longest to say out loud.

Most advisors — and I include myself, early on — collapse the client's judgment instead of protecting it.

It happens quietly. A client arrives carrying a decision. The advisor, experienced and eager to help, hands back a recommendation so clean that the client's own thinking never has to show up.

It feels like good service. It's actually a small theft.

The client leaves with an answer they did not build. When it is tested, they may not know what holds it up. They return for the next answer, and the advisor becomes the thinking.

I did that to people before I understood what I was doing. When I finally saw it, I made a rule for myself that became the spine of everything I built after: give them the structure, the sequence, and the hard question — then hand the decision back.

The decision belongs to the person who has to live with it.

If one strong voice can become the answer, why use a room of voices? Because disagreement prevents any single voice from taking that place.

The person sees one question pressed from several directions: where an argument is strong, where it caves, and which assumptions were left unsaid.

Instead of asking "what does the expert think?" the person can ask, "which of these arguments holds against my situation?" They watch, compare, and weigh rather than wait to be told.

The room provided the material. The person did the work.

The room doesn't decide. It returns the judgment to the person who brought the question.

That is the origin of the deliberation format: no single voice owns the answer, and disagreement remains visible.

The software did not come first. Before there was a platform, there was a governance manual: written decisions about what the practice would never do and how those decisions could be amended.

I wrote the rules first because institutions drift through reasonable exceptions that become precedents. The doctrine came before the code.

The code answers to the doctrine. Not the other way around.

Plainly:

The Roundtable is for a person carrying a consequential question that is actually theirs to answer — an operator, an owner, a principal — who wants perspectives without surrendering judgment.

It is not a content machine, a chatbot, or a productivity toy. It will not entertain you, chase you, or take the question off your hands.

Its boundary is narrow: six perspectives examine one question, disagreement is preserved, and the judgment remains yours.

Everything I've built comes back to one picture: the person sitting across the table with all the information and no clear next step.

Some days, that person was me.

Uncertainty is not a character flaw. It is what can happen when a consequential question meets too much noise and not enough structure.

If you are carrying a question whose judgment remains yours, the Roundtable is what I built to hold it from more than one side.