I help you figure out what to build. Then I build it. 48 products (and counting) shipped | 4 companies founded AI where it actually helps SLC 🏔️ | AR 🏕️
Salt Lake City Area, Utah
Joined February 2009
- Tweets2.5K
- Following987
- Followers464
- Likes1K
Bambu's H3C launches Nov 3.
Nine tools on a rack that drops down out of the way.
Part of me says I don't need it.
The other part is already measuring the shelf.
Powder Mountain just closed its summer trails for the season.
Snowbasin says 34 days until opening.
That awkward stretch where the bike's still out and the skis are staring at me from the garage.
Ogden folks: what's still riding well down low?
No. 2 BYU at UCF today. 1:30 PM Mountain on FOX.
The highest-ranked team ever to visit the Bounce House.
Last time the Cougs were ranked this high, it was 1984.
No pressure, Bear.
Go Cougs.
Most AI "automation" just hands you a smaller pile.
That's not the goal.
One team flipped it: a referral intake assistant handles the routine stuff, and coordinators only see the exceptions.
Not the pile. The exceptions.
AI does the donkey work. People make the calls.
I protect my mornings like revenue.
Not because I'm a morning person. I'm a night owl.
But one "quick check" of email can eat up my best thinking.
So the admin waits, AI sorts it first, and I only review the exceptions.
Your best hours aren't for your inbox. Defend them.
Eleven spreadsheets.
That's how one team I worked with ran dispatch.
Eleven spreadsheets isn't a system. It's a single point of failure with conditional formatting.
We replaced them with one board.
They didn't need fancier software. They needed one place to look.
I don't want AI to think for me.
I want it to do my donkey work.
Pull the numbers. Draft the follow-up. Sort the inbox before I've had coffee.
Then I show up for the part that's actually mine:
the call, the taste, the "no."
AI can carry the load. I'm still picking the trail.
Quick test for any doc:
Does someone grab it mid-task?
Or promise to "review it later"?
"Later" means never. Redesign it.
Every strategy doc needs a "Not This" list.
Without boundaries, you have a to-do list.
With them, you have an actual decision.
What you're NOT doing is the strategy.
A 30-page SOP isn't thorough.
It's deferred decision-making.
If your doc needs a "refresher meeting," it's not a strategy. It's a storage unit.
The sign your doc is actually working: it's messy.
Clean margins = nobody's using it.
Beat-up and edited = it's in the workflow.
Stop optimizing for completeness. Optimize for action.
The one-screen strategy template that replaced all my bloated docs:
Three sections. One screen. Here's how it works:
The "Not This" list turns a to-do list into actual strategy.
It's where you document what you're NOT doing - which is where most teams fall apart.
I spent years building the wrong kind of documents.
PRDs that went from 5 pages to 26 to 113.
SOPs that no one opened twice.
Strategy decks that needed "refresher meetings."
Here's what finally fixed it:
Counterintuitive sign a doc is working?
It gets messy. People write in margins. Skip sections. Adapt on the fly.
Pristine docs aren't being used.
Beat-up docs are.