Updated 14 September, 2026 · 2 min read
Why Most AI Projects Fail Before They Launch, and How to Avoid It
Agree a business baseline and a testable outcome before the first sprint.
Field notes
Practical perspectives on AI strategy, model deployment, GenAI architecture, and what is actually working in production. Written for builders, with the rough edges left in.
Pick a thread. The posts inside the same thread compound, so reading two or three in order is more useful than one.
How retrieval, evaluation, and tool-use actually play out in production, beyond the demo.
Training, evaluation, drift, and the unglamorous infra that keeps models honest after launch.
Frontend patterns, latency budgets, observability, the engineering layer most posts skip.
Updated 14 September, 2026 · 2 min read
Agree a business baseline and a testable outcome before the first sprint.
Updated 14 September, 2026 · 2 min read
Start with one repeatable workflow and preserve a human path for exceptions.
Updated 14 September, 2026 · 2 min read
Scope a thin end-to-end feature and test it with representative inputs before expanding.
22 April, 2025 · 1 min read
Audit provenance, missing values, labels, and train–test leakage before tuning models.
10 May, 2025 · 1 min read
Define ownership and review routines before adding delivery capacity.
28 May, 2025 · 1 min read
Evaluate the complete tool-using workflow, including retries and approval boundaries.
12 June, 2025 · 1 min read
Bring security, privacy, and relevant legal specialists into the design process early.
30 June, 2025 · 1 min read
Measure whether the correct authorized source is retrieved before judging the answer.
15 July, 2025 · 1 min read
Make the first milestone an observable user journey with explicit acceptance criteria.
11 August, 2025 · 1 min read
Evaluate the customer problem and unit economics before choosing a product category.
18 September, 2025 · 2 min read
Estimate cost per completed task using current provider prices and your actual workload.
14 October, 2025 · 2 min read
Test reasoning models against simpler baselines on the decisions your application needs.
10 November, 2025 · 2 min read
Introduce retrieval complexity only when an evaluation set shows what the simpler system misses.
28 November, 2025 · 2 min read
Check current official requirements with counsel; obligations depend on your role and use case.
15 December, 2025 · 2 min read
Choose model size after comparing task quality, memory, latency, and operating requirements.
8 January, 2026 · 2 min read
Treat MCP integration as an access-controlled system boundary, not automatic permission to act.
22 January, 2026 · 2 min read
Evaluate each input modality and the combined task, including failures and missing inputs.
5 February, 2026 · 2 min read
Test noisy speech, interruptions, consent, and human transfer before automating live calls.
18 February, 2026 · 2 min read
Keep each agent’s responsibility bounded and make actions observable and reversible where possible.
28 February, 2026 · 2 min read
Use coding assistants to support engineering judgment, not replace verification and ownership.
7 March, 2026 · 2 min read
Compare current model versions on your evaluation set; do not choose from headline price ratios.
13 March, 2026 · 2 min read
Separate untrusted input from instructions and enforce permissions outside the model.
Updated 14 September, 2026 · 3 min read
Ask prospective partners for attributable project evidence, delivery ownership, and references.
20 March, 2026 · 2 min read
Budget for data preparation, integration, evaluation, and post-launch operation as well as development.
24 March, 2026 · 1 min read
Plan a lifecycle from data audit to evaluation, release, monitoring, and controlled retraining.
27 March, 2026 · 1 min read
Match the engagement model to the role’s duration, specialization, and ownership requirements.
31 March, 2026 · 1 min read
Compare delivery models by coordination cost and accountability, not just hourly rates.
4 April, 2026 · 1 min read
Fit the feature to an existing user workflow and define its fallback before launch.
8 April, 2026 · 1 min read
Version the inputs and artifacts, and define recovery actions alongside monitoring alerts.
12 April, 2026 · 1 min read
Start with the operational bottleneck and ownership model before deciding to build custom software.
16 April, 2026 · 1 min read
Ground support answers in current policies and make escalation an intentional part of the experience.
19 April, 2026 · 1 min read
Tie visual detections to a specific action and evaluate them under real operating conditions.
22 April, 2026 · 1 min read
A useful consulting engagement produces decisions, evaluation criteria, and a delivery roadmap.