The Shape of Data: Questions Lost at Capture
A daily revenue total can't tell you which products a customer bought together. Once the order lines are gone, a larger database can't recover them.
The AndyDataGuy wiki holds dozens of essays across five topics, from sales and growth to AI and technical development.
A customer who pays for a year of software gives the seller cash before the seller has finished the work. That cash can fund the company. The customer still needs the installation, the support and the result they bought, and a refund promise creates another obligation the seller has to fund. Those obligations determine whether the offer works.
A premium menswear brand was sending cold traffic toward $400 to $500 jeans. My CRO work changed the entry offer to a keychain, introduced the jeans along the page, and brought them together in a bundle. The experiment concerned how a stranger became a customer, including what happened at checkout. A different hero image would've left that purchase decision intact.
Landing page planning starts with the visitor and offer. Marketers can check the first phone screen against the promise that brought someone there.
Conversion funnel design connects buyer research to page decisions for marketers. Keep customer quotations beside each proposed change and its expected result.
Consider a customer who buys a product and then receives another email asking them to buy the same product. The automation kept its schedule. The customer moved on.
What unfair beginnings leave you to work with, and how to choose, test, and learn from the next move.
Retrieval engineers can compare two paths on the same questions. The proposed twin test helps distinguish missing sources, failed retrieval and evidence the model ignored.
Hyperrelevance Cartography helps proposal writers interpret a buyer's silence. An unopened message and weak proof need different checks before another revision.
A daily revenue total can't tell you which products a customer bought together. Once the order lines are gone, a larger database can't recover them.
A daily revenue total can't tell you which products shared a customer's basket. That information lives in the order lines and their shared order identifier. A graph, a vector index and a larger warehouse all face the same limit once those records are gone. Choosing a data shape means deciding which distinctions to retain, which questions to make convenient, and which obligations the system must enforce.
A change compiles, passes code review and gets merged. The page it was meant to fix is still wrong. Each person completed the job they were given, but nobody checked the result the customer would receive. A useful workflow has to name the evidence that permits work to move, who evaluates it and where the work goes when that evidence is missing.
Customer service and tech support teams can distinguish account decisions from technical investigations. Case histories and named owners keep escalations connected to the customer's outcome.
CRM automation connects recorded sales events to work for reps. Define stage changes and agree which system owns each shared field before adding rules.
Sales enablement gives agency owners a way to teach their sales decisions. Connect selected call recordings and playbook rules to the work a new rep practices.
Support operations leaders can set separate commitments for first response and final resolution. Accurate triage and a maintained knowledge base address different sources of repeated work.
I want a science fiction universe where economics and culture shape civilizations and each story changes the world that later stories inherit.
Voice compiler methods help agencies record rules for each client and channel. An equipment dealer's approved captions show how those rules differ.
The Standard Model of Effective Media connects familiar details to difficult subjects. Creators test the connection against what audiences understand and do.
An audience can agree with everything you make and still leave with the same problem it brought. The relationship I want to build asks more of the work: give someone a better account of their situation, something they can use outside the exchange, and enough room to decide what to do with it. Applause tells you that a person responded. Finding out what changed takes a different kind of attention.
Brand voice guidelines help writers choose language for different readers. A portrait studio's rejected campaign copy shows why that choice needs evidence.
The agents finish their parts. The buyer still has to make the result usable.
A practical system for connecting agent work with evidence and using each result to guide the next attempt
Why AI warnings should protect people or improve judgment without needlessly obstructing the question they were supposed to help answer
I want a science fiction universe where economics and culture shape civilizations and each story changes the world that later stories inherit.
Voice compiler methods help agencies record rules for each client and channel. An equipment dealer's approved captions show how those rules differ.
A daily revenue total can't tell you which products a customer bought together. Once the order lines are gone, a larger database can't recover them.
A daily revenue total can't tell you which products shared a customer's basket. That information lives in the order lines and their shared order identifier. A graph, a vector index and a larger warehouse all face the same limit once those records are gone. Choosing a data shape means deciding which distinctions to retain, which questions to make convenient, and which obligations the system must enforce.
The Shape of Data helps finance teams explain past decisions. A commission example distinguishes the corrected deal amount from the value used to calculate payment.
A customer who pays for a year of software gives the seller cash before the seller has finished the work. That cash can fund the company. The customer still needs the installation, the support and the result they bought, and a refund promise creates another obligation the seller has to fund. Those obligations determine whether the offer works.
The Standard Model of Effective Media connects familiar details to difficult subjects. Creators test the connection against what audiences understand and do.
For agent developers, objects and functions carry different responsibilities. A provider client manages connections while a conversation record remains data that either side can inspect.
A model subscription gives an agency access to a generator. The agency still has to decide whether a draft says something useful, whether it sounds like the person whose name will appear above it, and whether an edit quietly changed the claim. Those decisions are part of the machinery I want to own. The Content Compiler is my proposed way to make them inspectable and repeatable without giving an editor permission to rewrite everything.
Data mesh handoffs test whether agent teams preserve usable context. A replacement worker needs business meanings and approval authority alongside a dataset name.
An audience can agree with everything you make and still leave with the same problem it brought. The relationship I want to build asks more of the work: give someone a better account of their situation, something they can use outside the exchange, and enough room to decide what to do with it. Applause tells you that a person responded. Finding out what changed takes a different kind of attention.
A premium menswear brand was sending cold traffic toward $400 to $500 jeans. My CRO work changed the entry offer to a keychain, introduced the jeans along the page, and brought them together in a bundle. The experiment concerned how a stranger became a customer, including what happened at checkout. A different hero image would've left that purchase decision intact.
Customer service and tech support teams can distinguish account decisions from technical investigations. Case histories and named owners keep escalations connected to the customer's outcome.
Landing page planning starts with the visitor and offer. Marketers can check the first phone screen against the promise that brought someone there.
Showing 12 of 51
Every Sunday: the week's best note, the worst note I caught myself almost publishing, and one thing I read that changed my mind. No spam. If you're subscribing because you want my newsletter to be your AI-tactics feed, unsubscribe. I write about whatever I'm building or breaking that week. Some weeks it's marketing. Some weeks it's distributed systems. Most weeks both.
Longer reads cover intelligence, attention and audience relationships.