The TWIMCO notebook
Field notes.
Useful observations from inside the work.
For people building a better way.
385 notes

Fixed price or time and materials? Price the uncertainty, not the project.
Ask three development shops for a quote on the same app and you may get a fixed price, an hourly rate and a question back. Each one is a different bet about who carries the unknowns. Here's how to tell which bet suits the work you actually have.
Read the note ↗︎
Before you replace the dispatch whiteboard, write down everything it does.
Magnets for technicians, columns for the day, a red marker for anything urgent. It looks old-fashioned, and the plan is to replace it with scheduling software. Spend a week noticing what that board quietly does first, or the new system will drop it.
Read the note ↗︎
A forecast that gives you one number is hiding the useful part.
"Can the AI just tell me how much to order?" It's the question we hear most from owners looking at demand forecasting. Here's roughly how the conversation goes, and why the answer we give is about ranges, sold-out days and who makes the call.
Read the note ↗︎
When people go around your marketplace, they're telling you something.
In the third message, a supplier slips in their mobile number. A week later, a regular customer stops booking through you but still seems to be getting the work done. Here's how to read those signs, and why blocking phone numbers rarely fixes what they mean.
Read the note ↗︎
The old version of your app is still on someone's phone.
Fix a bug on a website and everyone has the fix by lunchtime. Fix the same bug in a mobile app and some of your users will still be running the broken version next spring. Three what-ifs show why it pays to decide your update rules early.
Read the note ↗︎
Let people wait for the counter somewhere other than the lobby.
At eight in the morning the lobby fills, everyone takes a paper ticket, and nobody dares leave in case their number is called. It doesn't have to work like that. Five principles for letting people wait somewhere better, without losing anyone who doesn't carry a smartphone.
Read the note ↗︎
Some of your apps can edit your checkout.
One shopper on a Shopify keyboard store pressed Checkout and was quietly sent to a copy of the payment page on another site. He noticed. Most people wouldn't. Here's how to check where your own Checkout button really goes.
Read the note ↗︎
AI translation gets the sentence right and the size wrong.
Translating a whole catalog with AI now takes an afternoon, and most of it will read fine. Trouble hides in a handful of words: a size, a washing temperature, a returns promise, your own product names. Know which ones, and send only those to a person.
Read the note ↗︎
Most delivery problems were typed into the checkout.
A parcel comes back marked "insufficient address" because the apartment number never made it past the checkout form. Nobody did anything wrong, exactly. Seven plain rules keep that address true from the moment it's typed to the moment it's delivered.
Read the note ↗︎
Keep the Google button. Just don't make it the only way in.
Proton's "Don't sign in with Google" campaign is aimed at consumers, and it's back in people's feeds. If you own an app, the better question is what happens to a customer whose Google account stops working tomorrow.
Read the note ↗︎
Ask whose sales data your pricing tool learned from.
A lawsuit filed this month says McDonald's pricing software pooled private sales data from restaurants that are supposed to compete. Whatever the court decides, anyone shopping for pricing software now has a sharper first question to ask.
Read the note ↗︎
Count the logins that can reach your customers.
On Tuesday, ASOS customers got a push alert from the ASOS app saying ASOS had been hacked. The attackers sent it. They got in through one login to a marketing tool, not the store itself. If you run a store, here's how to find your own version of that login.
Read the note ↗︎
When a package goes bad, the obvious first move can hurt.
This week a poisoned JavaScript package came with a trap. Revoke the key it stole, and it wipes the computer it's on. If your site or store runs on JavaScript, here's what to sort out now and what to do first next time.
Read the note ↗︎
The morning after the store moves, customers find what the project didn't test.
Launch night went fine. The new storefront is faster and the team is proud of it. Then the support inbox opens at 8:15 the next morning, and the messages are about passwords, missing store credit and an old newsletter link, none of which were on the launch plan.
Read the note ↗︎
The AI summary dropped the one thing the customer said twice.
"Customer happy, wants to renew, send quote." It reads well, it's mostly true, and it leaves out the condition the whole renewal depends on. Reading one call against its summary, line by line, shows what to ask these tools for and what a person still has to check.
Read the note ↗︎
Rebuild somewhere else once, before you have to.
A Japanese cloud provider just told hundreds of customers their data probably can't be recovered, and that the only way back is a backup they kept themselves. Do you have one? Has anyone ever rebuilt from it?
Read the note ↗︎
A gift set is three promises sold as one.
When the candle sells out on its own, the holiday set that contains it often keeps selling. Bundles look like one product on the storefront and behave like several in the warehouse, and peak season is when that difference gets expensive.
Read the note ↗︎
Before a limited drop, decide who should end up with it.
Target's overnight Pokémon card drop went sideways again. If you sell anything in short runs, the real question isn't how fast your checkout is. It's who you want holding the box when it's over.
Read the note ↗︎
When someone leaves, the risk is in the accounts nobody listed.
Disabling a departing colleague's email takes a minute. Finding the vendor portal they logged into, the report that runs under their name and the subscription they paid for on expenses takes much longer, and it usually happens after something stops working.
Read the note ↗︎
A screener that tells people they don't qualify had better be right.
A few questions up front can save an applicant hours and save your staff a pile of applications that were never going to pass. It will also be wrong sometimes, and one kind of wrong is far more expensive than the other because nobody ever sees it.
Read the note ↗︎A familiar problem? Let’s look closer.
Tell us where you want to go. We’ll find the first thing worth changing.
Tell us about it ↗︎