What to Measure Before and After an Automation
Most organizations cannot prove their automation worked, because nobody wrote down what the before looked like. Twenty minutes of measurement in the week before...
Insights & Articles
Practical articles from the Albright Labs team on development, automation, and running a technology business.
Most organizations cannot prove their automation worked, because nobody wrote down what the before looked like. Twenty minutes of measurement in the week before...
Most automation vendors demo well. The demo tells you almost nothing about what it will be like to own the result in year two. The questions that actually separ...
The quote is the smallest number in an automation project. The costs that decide whether it pays back are the ones nobody puts on the proposal: the explaining, ...
Spreadsheets are excellent software, and most organizations run on them longer than they should. The failure is quiet: throughput capped by headcount, reconcili...
Most organizations pick their first automation project badly. They automate the process that annoys them most, rather than the one that would pay back first. Th...
Most software doesn't die from one bad decision. It dies from a long sequence of reasonable ones. Building software that survives five years is mostly about avo...
Plugin-driven content systems look cheap. They're cheap until the project is small. As an organization grows, the total cost of plugins, integrations, maintenan...
Code review in a long-lived codebase is partly archaeology. AI accelerates the surface-level checks, but the institutional history reviewers carry is exactly wh...
Software estimation is part research, part judgment, and part politics. AI helps with the research, struggles with the judgment, and has no role in the politics...
On a small dev team, every hour shows up in the schedule. AI saves real time in a narrow set of activities, mostly the unglamorous ones, and wastes time when ap...
Albright Labs
Tell us what you are trying to accomplish, what is in the way, and when you need it. We will take it from there.
A senior engineer reads it and replies within one business day.
or call +1 (610) 756-5060We use cookies to improve your experience, understand how the site is used, and measure our advertising. See our Cookie Policy.