The 3 corporate habits I kept as an owner

3 habits from my 12 years in corporate still run my business. Every meeting ends with an owner, every risky idea goes on 1 page, and I only automate what I already know how to do well.

Most advice for owners says to leave the corporate playbook behind. I kept 3 pages of it, because they work just as well with a team of 3 as with a team of 300.

This is for anyone running a small team, and for anyone in corporate who wants to see which habits are worth taking with them.

By the end, you'll know:

• the 1 question that ends every meeting at my company
• what goes on the 1-page version of a risky idea
• why "know what good looks like" comes before any AI handoff

1. Every meeting ends with who, what and by when

Before anyone leaves, I ask: who is doing what, by when? I leave every meeting with the who, what, when, where and why, and the summary goes out the same day. Clear ownership drives results.

The small-business version is simple. A task with no name next to it is a task nobody has. "We should look into that" gets a name and a date, or it gets dropped on purpose. Either is better than 3 people each assuming one of the others has it.

2. A risky idea goes on 1 page first

Before I pitch anything risky, to a client, a partner or my own team, I write 4 short items: the problem, how the idea fixes it, the result I expect, and the risk of doing nothing.

Writing it down is where weak ideas fall apart, privately and cheaply. If I can't fill in the "result" line with a number or a date, I'm not ready to say it out loud. And when the idea survives the page, the pitch is already written.

3. Know what good looks like before you hand it off

I'm happy to hand off notes, summaries and first drafts, because I know what a good one looks like and can spot a bad one in seconds. That's the order: judge first, then automate.

Plenty of companies are learning this the expensive way. A report released Oct. 29 by talent company SHL surveyed more than 2,000 working adults in the U.S. and U.K. and found that more than half had seen "AI rebounding": a company replaces workers with AI, then tries to bring them back. In the U.S., nearly 1 in 5 said they had firsthand experience. If called back, 51% said they would want a "substantial" raise, and 42% would want a job-security guarantee. Gartner predicts that by 2029, 30% of workers terminated or replaced by AI will be rehired, often at a higher cost (HR Dive, Nov. 5, 2026).

SHL sells talent assessments, the survey reports what people say they would demand, and Gartner's number is a prediction. The pattern still holds up. SHL's own line: "AI rebounding is what happens when a company automates a role before it has genuinely assessed the human capability inside it."

Before you hand a task, or a whole role, to AI:

1. Write down everything the person does in a week, including what nobody asked them to do, like calming an upset customer or catching an error before it goes out.
2. Pilot the AI on 1 task for 30 days while that person is still there.
3. Decide what "it worked" means as a number.
4. Tell your team what AI will change and what it won't.

Then put the whole decision on the 1 page from habit 2, including the risk of it not working.

Next week

The lesson I wish I'd learned first: don't be the hardest worker. More on that next week.

If you want a second set of eyes on a meeting routine or on what to hand to AI first, grab a time with me.