Writing
Notes on the work
How I work, and why these systems succeed or fail. Mostly drawn from having been on the other end of them. Short, occasional, and never written to fill a schedule.
-
Where it runs, and what I can see
The first thing every company asks: where does this live, and what can you see? The whole answer, and the four ways it can be set up.
-
A party game, run like a business system
I rebuilt a party game to run on this company’s Microsoft accounts. Where it runs, how its price was set from measured cost, and why it has no ticket system.
-
One number, every month
One flat monthly fee, no timesheet, and the short list of what it doesn't cover.
-
What I ask before I build anything
Six questions I ask before anything gets built, in the order I ask them.
-
Why you should own your own data
Most consultants and software vendors end up holding their clients' data. It is a business model, not a technical necessity.
-
Nobody is doing your exercises
Clinicians know most patients skip the home program. The same thing happens to the software you buy for your crews, for the same four reasons, and it is not a discipline problem.
New notes go out by RSS. Nothing to sign up for and no mailing list.
Something here sound like your business?
Tell me which piece, and what the gap looks like from where you sit.