The reading room · Digna Legi
AI, tools and transformation
/100
80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.
Evidence-reviewed score based on available publisher text. The piece is analytical and historically reasoned, but the supplied text does not include primary research data.
Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.
How scoring works →This brief · about 3 min with detail
Why read this
AI may lower the cost of improvising tools, while transformation still depends on finding, standardizing, and spreading better work practices.
AI brief · Checked against source text
The main idea
The central claim is that AI will not simply dissolve enterprise software into spontaneous automation. Evans argues that companies accumulate software because work moves between improvised fixes and institutionalized systems as tasks become repeated, risky, shared, and valuable. AI adds new improvisational surfaces and expands existing tools, but transformation still depends on seeing the problem, designing the right intervention, and getting organizations to adopt it.
Some background helpful. Basic familiarity with enterprise software, SaaS, spreadsheets, and AI chatbots.
Go a little deeper
Tool creation is not the scarce skill
The article separates the ability to generate software from the ability to recognize what should be changed. People close to a job may be excellent practitioners without thinking like tool builders, so the automatable task can remain visible yet unnamed. Forward-deployed engineers matter in this account because they combine builder instincts with enough proximity to notice latent opportunities.
Improvisation becomes infrastructure
Evans’s strongest mechanism is the movement from loose workarounds to formal systems. Email, spreadsheets, shared folders and calls handle exceptions well, but repetition, shared use, revenue exposure and risk eventually demand audit, security, maintenance and accountability. That explains why firms end up with many applications rather than one universal platform.
AI moves thresholds, not the basic cycle
AI is placed inside the existing rhythm of bundling and unbundling. It may let a small firm stay in Google Sheets longer, make a chatbot a new freeform workspace, or create demand for a new vertical SaaS product. The decision remains whether a task belongs in an improvised space or a dedicated system.
Pilots do not equal transformation
Giving everyone a general-purpose tool can scale access without scaling change. The article compares AI rollout to giving employees spreadsheets or browsers: useful, but not sufficient to redesign invoice processing, supply chains or e-commerce. Structural transformation requires asking what the technology means for operations and competitive economics, not only running isolated pilots.
A case from the article
Recruiting across company sizes
Hiring graduates shows the improvised-to-institutionalized spectrum. A very large firm uses dedicated recruiting software because the process is repeated at scale, while a small firm can manage a handful of hires with email, folders and Sheets. Growth can push the small firm toward SaaS, yet even a team inside the large firm may return to Sheets when formal software is too rigid.
How the case is made
The case is made through enterprise-software observation, historical analogy to PCs, spreadsheets and browsers, and concrete workflow examples.
Where the idea has limits
The argument addresses company transformation and workflow automation, not whether particular AI tools are useful for individual tasks or whether specific vendors will win.
A question to take away · from Digna Legi
Which workflows in your organization are improvised because they are rare, and which are improvised because nobody has noticed they became infrastructure?
What the original adds
The source adds a detailed institutionalized-versus-improvised spectrum, examples such as hiring workflows and Carta, and a board-level distinction among deployment, operational change, and competitive threat.
About this brief
AI-written, then separately checked for source support, useful detail and clarity. The author’s claims and our editorial question are kept separate. The original remains the author’s work. How we select and summarise →
How was this brief?
Rate this summary, separately from the author’s article.
Optional. Saved in this browser; shared only if you allow analytics.
How was the original article?
Rate the author’s original after reading it.
Optional. Saved in this browser; shared only if you allow analytics.
Digna legi. Worth reading.