<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>AAhouse AI implementation journal</title><link>https://www.aahouse.com/blog/</link><description>Original AI implementation analysis for self-employed professionals and small businesses</description><language>en</language><item><title>Choose your first AI workflow before choosing a tool</title><link>https://www.aahouse.com/blog/choose-first-ai-workflow/</link><guid>https://www.aahouse.com/blog/choose-first-ai-workflow/</guid><description>A practical way to narrow a broad AI ambition into a testable business improvement.</description></item><item><title>Interview staff without selling them an AI answer</title><link>https://www.aahouse.com/blog/workflow-interview-without-leading/</link><guid>https://www.aahouse.com/blog/workflow-interview-without-leading/</guid><description>Discover operational friction without steering every answer toward automation.</description></item><item><title>AI readiness is a set of conditions, not a trophy score</title><link>https://www.aahouse.com/blog/ai-readiness-without-maturity-score/</link><guid>https://www.aahouse.com/blog/ai-readiness-without-maturity-score/</guid><description>Use readiness checks to identify the next constraint rather than rank your business.</description></item><item><title>Write a one-page AI pilot charter</title><link>https://www.aahouse.com/blog/pilot-charter-one-page/</link><guid>https://www.aahouse.com/blog/pilot-charter-one-page/</guid><description>Prevent scope drift by agreeing on a decision, a boundary, and a fallback.</description></item><item><title>A compelling AI demo is not yet a business case</title><link>https://www.aahouse.com/blog/why-ai-demo-not-business-case/</link><guid>https://www.aahouse.com/blog/why-ai-demo-not-business-case/</guid><description>Move from a polished example to evidence about everyday performance.</description></item><item><title>Time saved is not automatically cash saved</title><link>https://www.aahouse.com/blog/ai-roi-capacity-versus-cash/</link><guid>https://www.aahouse.com/blog/ai-roi-capacity-versus-cash/</guid><description>Build a value model that distinguishes capacity, cash, and service quality.</description></item><item><title>The full cost of a small-business AI workflow</title><link>https://www.aahouse.com/blog/total-cost-ai-small-business/</link><guid>https://www.aahouse.com/blog/total-cost-ai-small-business/</guid><description>Look beyond the monthly model bill to understand sustainable delivery.</description></item><item><title>Build, buy, or configure: make the comparison fair</title><link>https://www.aahouse.com/blog/build-buy-configure-ai/</link><guid>https://www.aahouse.com/blog/build-buy-configure-ai/</guid><description>Choose the smallest sustainable solution rather than the most impressive architecture.</description></item><item><title>What a fixed-scope AI proposal should actually fix</title><link>https://www.aahouse.com/blog/fixed-scope-ai-proposal/</link><guid>https://www.aahouse.com/blog/fixed-scope-ai-proposal/</guid><description>Turn a headline price into a clear agreement about work and acceptance.</description></item><item><title>Release the AI budget in stages</title><link>https://www.aahouse.com/blog/ai-budget-stage-gates/</link><guid>https://www.aahouse.com/blog/ai-budget-stage-gates/</guid><description>Fund the next piece of evidence before funding a broad platform.</description></item><item><title>Train for the job, not for a tour of AI features</title><link>https://www.aahouse.com/blog/role-based-ai-training/</link><guid>https://www.aahouse.com/blog/role-based-ai-training/</guid><description>Design practice around the decisions staff must make after training.</description></item><item><title>Give your AI champion a charter, not a second full-time job</title><link>https://www.aahouse.com/blog/ai-champion-charter-small-team/</link><guid>https://www.aahouse.com/blog/ai-champion-charter-small-team/</guid><description>Make peer support useful without confusing enthusiasm with accountability.</description></item><item><title>Turn AI office hours into a problem-solving loop</title><link>https://www.aahouse.com/blog/office-hours-ai-support/</link><guid>https://www.aahouse.com/blog/office-hours-ai-support/</guid><description>Use recurring questions to improve the workflow rather than repeat demonstrations.</description></item><item><title>Measure AI adoption without turning it into surveillance</title><link>https://www.aahouse.com/blog/ai-adoption-without-surveillance/</link><guid>https://www.aahouse.com/blog/ai-adoption-without-surveillance/</guid><description>Collect enough evidence to improve work while respecting employee trust.</description></item><item><title>Watch the NIST AI risk explainer with a real workflow in hand</title><link>https://www.aahouse.com/blog/nist-video-working-session/</link><guid>https://www.aahouse.com/blog/nist-video-working-session/</guid><description>Turn an official introductory video into a focused team discussion.</description></item><item><title>Bilingual AI adoption needs more than translated buttons</title><link>https://www.aahouse.com/blog/bilingual-ai-adoption-team/</link><guid>https://www.aahouse.com/blog/bilingual-ai-adoption-team/</guid><description>Plan terminology, review, and handoffs for the people doing the work.</description></item><item><title>Decide when an AI pilot should stop</title><link>https://www.aahouse.com/blog/pilot-stop-criteria/</link><guid>https://www.aahouse.com/blog/pilot-stop-criteria/</guid><description>Stopping can be a successful decision when a bounded experiment answers its question.</description></item><item><title>Design a pilot comparison that can challenge your hopes</title><link>https://www.aahouse.com/blog/ai-pilot-comparison-design/</link><guid>https://www.aahouse.com/blog/ai-pilot-comparison-design/</guid><description>Avoid attributing every improvement to the tool you wanted to succeed.</description></item><item><title>Read AI productivity research without importing its headline</title><link>https://www.aahouse.com/blog/read-ai-productivity-research/</link><guid>https://www.aahouse.com/blog/read-ai-productivity-research/</guid><description>A study is a starting point for questions, not a ready-made forecast for your company.</description></item><item><title>Five questions to carry into an executive AI interview</title><link>https://www.aahouse.com/blog/ai-executive-video-questions/</link><guid>https://www.aahouse.com/blog/ai-executive-video-questions/</guid><description>Use an industry interview to challenge assumptions rather than copy a roadmap.</description></item><item><title>Questions to ask before signing an AI implementation proposal</title><link>https://www.aahouse.com/blog/questions-before-ai-vendor-contract/</link><guid>https://www.aahouse.com/blog/questions-before-ai-vendor-contract/</guid><description>Use procurement to expose delivery responsibilities, not only compare headline prices.</description></item><item><title>A handover your team can actually use</title><link>https://www.aahouse.com/blog/ai-handover-that-team-can-use/</link><guid>https://www.aahouse.com/blog/ai-handover-that-team-can-use/</guid><description>Documentation should support ordinary operation and recovery, not just describe the architecture.</description></item><item><title>Expand AI after repeatable results, not after enthusiasm</title><link>https://www.aahouse.com/blog/expand-ai-after-repeatable-results/</link><guid>https://www.aahouse.com/blog/expand-ai-after-repeatable-results/</guid><description>Use a narrow success to learn what can travel to the next team.</description></item><item><title>Services first, platform later: what must repeat?</title><link>https://www.aahouse.com/blog/services-first-platform-later/</link><guid>https://www.aahouse.com/blog/services-first-platform-later/</guid><description>Use customer work to discover a product boundary instead of building a generic app generator too early.</description></item><item><title>Write an AI success story that a customer can trust</title><link>https://www.aahouse.com/blog/ai-success-story-evidence/</link><guid>https://www.aahouse.com/blog/ai-success-story-evidence/</guid><description>Explain scope, evidence, and limits instead of presenting an exceptional example as a universal promise.</description></item><item><title>Before the chatbot: audit the knowledge it will use</title><link>https://www.aahouse.com/blog/audit-knowledge-before-chatbot/</link><guid>https://www.aahouse.com/blog/audit-knowledge-before-chatbot/</guid><description>A practical inventory that exposes ownership, gaps, and duplicate guidance before indexing begins.</description></item><item><title>When two policies disagree, the model should not cast the deciding vote</title><link>https://www.aahouse.com/blog/resolve-conflicting-company-policies/</link><guid>https://www.aahouse.com/blog/resolve-conflicting-company-policies/</guid><description>Treat conflicting instructions as a content-governance problem before adjusting prompts.</description></item><item><title>A small data dictionary can prevent a large extraction mistake</title><link>https://www.aahouse.com/blog/business-data-dictionary-before-extraction/</link><guid>https://www.aahouse.com/blog/business-data-dictionary-before-extraction/</guid><description>Define what each field means before asking AI to fill it.</description></item><item><title>Before changing OCR models, check the incoming scan</title><link>https://www.aahouse.com/blog/ocr-input-quality-first/</link><guid>https://www.aahouse.com/blog/ocr-input-quality-first/</guid><description>A controlled input-quality experiment is often more useful than another vendor demo.</description></item><item><title>A correct number in the wrong row is still a wrong extraction</title><link>https://www.aahouse.com/blog/table-extraction-row-integrity/</link><guid>https://www.aahouse.com/blog/table-extraction-row-integrity/</guid><description>Validate relationships and table structure before trusting extracted totals.</description></item><item><title>Missing fields need a workflow, not a creative answer</title><link>https://www.aahouse.com/blog/missing-fields-not-invented-values/</link><guid>https://www.aahouse.com/blog/missing-fields-not-invented-values/</guid><description>Design extraction so uncertainty becomes a request for clarification rather than invented data.</description></item><item><title>A source link is the start of provenance, not the end</title><link>https://www.aahouse.com/blog/answer-provenance-beyond-link/</link><guid>https://www.aahouse.com/blog/answer-provenance-beyond-link/</guid><description>Make an answer traceable to the passage, version, and permission context that supported it.</description></item><item><title>Choose document boundaries around the questions people ask</title><link>https://www.aahouse.com/blog/chunk-documents-around-business-questions/</link><guid>https://www.aahouse.com/blog/chunk-documents-around-business-questions/</guid><description>Compare chunking strategies against real retrieval needs instead of chasing a universal token size.</description></item><item><title>Contextual retrieval: add orientation, not hidden policy</title><link>https://www.aahouse.com/blog/contextual-retrieval-not-extra-instructions/</link><guid>https://www.aahouse.com/blog/contextual-retrieval-not-extra-instructions/</guid><description>Use document context carefully and test whether it improves retrieval for your own corpus.</description></item><item><title>Product codes need more than semantic similarity</title><link>https://www.aahouse.com/blog/hybrid-search-for-product-codes/</link><guid>https://www.aahouse.com/blog/hybrid-search-for-product-codes/</guid><description>A retrieval test that gives exact identifiers and ordinary language different jobs.</description></item><item><title>Bilingual retrieval is not the same as translating the answer</title><link>https://www.aahouse.com/blog/bilingual-retrieval-is-not-translation/</link><guid>https://www.aahouse.com/blog/bilingual-retrieval-is-not-translation/</guid><description>Test whether questions and evidence can cross languages before polishing the interface.</description></item><item><title>Hong Kong, Taiwan, and Macao terms belong in the search test</title><link>https://www.aahouse.com/blog/regional-terms-company-search/</link><guid>https://www.aahouse.com/blog/regional-terms-company-search/</guid><description>Regional interface wording should lead to the same business evidence when the meaning is the same.</description></item><item><title>Protect knowledge before it reaches the model</title><link>https://www.aahouse.com/blog/retrieval-permissions-before-generation/</link><guid>https://www.aahouse.com/blog/retrieval-permissions-before-generation/</guid><description>A polite refusal prompt is not a substitute for permission-aware retrieval.</description></item><item><title>How fresh does your knowledge assistant need to be?</title><link>https://www.aahouse.com/blog/knowledge-refresh-service-level/</link><guid>https://www.aahouse.com/blog/knowledge-refresh-service-level/</guid><description>Choose refresh commitments from business consequences instead of assuming every document is live.</description></item><item><title>Deleting a file does not finish the knowledge-removal workflow</title><link>https://www.aahouse.com/blog/delete-document-from-ai-knowledge/</link><guid>https://www.aahouse.com/blog/delete-document-from-ai-knowledge/</guid><description>Check derived indexes, previews, and traces when information should no longer be available.</description></item><item><title>Build an evaluation set from the work, not the demo</title><link>https://www.aahouse.com/blog/build-rag-evaluation-set/</link><guid>https://www.aahouse.com/blog/build-rag-evaluation-set/</guid><description>A small, well-labeled test set can reveal whether retrieval and generation fail for different reasons.</description></item><item><title>An answer can be correct while its citation is wrong</title><link>https://www.aahouse.com/blog/evaluate-citation-support/</link><guid>https://www.aahouse.com/blog/evaluate-citation-support/</guid><description>Review citation support as a separate quality dimension.</description></item><item><title>Teach the assistant how to say it does not know usefully</title><link>https://www.aahouse.com/blog/design-useful-abstention/</link><guid>https://www.aahouse.com/blog/design-useful-abstention/</guid><description>An explicit uncertainty path is part of service design, not an embarrassing failure screen.</description></item><item><title>Using AI to grade AI still needs a human calibration pass</title><link>https://www.aahouse.com/blog/llm-judge-human-calibration/</link><guid>https://www.aahouse.com/blog/llm-judge-human-calibration/</guid><description>Treat judge models as triage tools until their decisions match a clear business rubric.</description></item><item><title>Use embedding leaderboards to shortlist, not to sign off</title><link>https://www.aahouse.com/blog/embedding-leaderboard-local-test/</link><guid>https://www.aahouse.com/blog/embedding-leaderboard-local-test/</guid><description>Choose retrieval models against local language, identifiers, and operating constraints.</description></item><item><title>Choose models by the knowledge task, not by one flagship name</title><link>https://www.aahouse.com/blog/model-routing-by-knowledge-task/</link><guid>https://www.aahouse.com/blog/model-routing-by-knowledge-task/</guid><description>Separate parsing, retrieval, classification, and answer generation in your evaluation.</description></item><item><title>Control RAG cost by improving evidence selection first</title><link>https://www.aahouse.com/blog/rag-cost-context-budget/</link><guid>https://www.aahouse.com/blog/rag-cost-context-budget/</guid><description>More retrieved text is not automatically more useful context.</description></item><item><title>A spreadsheet is not just a document with cells</title><link>https://www.aahouse.com/blog/spreadsheet-knowledge-needs-calculation/</link><guid>https://www.aahouse.com/blog/spreadsheet-knowledge-needs-calculation/</guid><description>Separate narrative retrieval from calculations and live business records.</description></item><item><title>How to watch a hybrid-search demo without mistaking it for proof</title><link>https://www.aahouse.com/blog/watch-hybrid-retrieval-with-test-plan/</link><guid>https://www.aahouse.com/blog/watch-hybrid-retrieval-with-test-plan/</guid><description>Use Microsoft’s documentation and its embedded explainer as a learning resource, then design a local experiment.</description></item><item><title>When the diagram carries the instruction, text-only retrieval is incomplete</title><link>https://www.aahouse.com/blog/multimodal-document-review/</link><guid>https://www.aahouse.com/blog/multimodal-document-review/</guid><description>Treat visual evidence as a separate data-readiness and evaluation problem.</description></item><item><title>Retry an AI workflow without creating another order</title><link>https://www.aahouse.com/blog/retry-without-duplicate-orders/</link><guid>https://www.aahouse.com/blog/retry-without-duplicate-orders/</guid><description>A proposed operation ledger separates business intent from network attempts.</description></item><item><title>Put a verified inbox in front of webhook-driven AI</title><link>https://www.aahouse.com/blog/webhook-inbox-before-ai/</link><guid>https://www.aahouse.com/blog/webhook-inbox-before-ai/</guid><description>Separate receipt, authenticity, and business processing in an event-driven integration.</description></item><item><title>Test disconnect before connecting the next AI integration</title><link>https://www.aahouse.com/blog/oauth-offboarding-rehearsal/</link><guid>https://www.aahouse.com/blog/oauth-offboarding-rehearsal/</guid><description>OAuth onboarding needs an equally deliberate offboarding path.</description></item><item><title>Tenant isolation needs a test map, not just a tenant column</title><link>https://www.aahouse.com/blog/tenant-isolation-test-map/</link><guid>https://www.aahouse.com/blog/tenant-isolation-test-map/</guid><description>Follow customer data through queries, files, jobs, and exports.</description></item><item><title>A document download link is part of your permission system</title><link>https://www.aahouse.com/blog/attachment-access-lifecycle/</link><guid>https://www.aahouse.com/blog/attachment-access-lifecycle/</guid><description>Treat uploads, previews, and downloads as one access lifecycle.</description></item><item><title>An invoice cannot authorize your AI agent</title><link>https://www.aahouse.com/blog/document-instructions-not-authority/</link><guid>https://www.aahouse.com/blog/document-instructions-not-authority/</guid><description>Reduce the damage of prompt injection by separating data interpretation from execution authority.</description></item><item><title>Write a contract for every tool your agent can call</title><link>https://www.aahouse.com/blog/agent-tool-contracts/</link><guid>https://www.aahouse.com/blog/agent-tool-contracts/</guid><description>A narrow tool interface turns broad language into bounded operations.</description></item><item><title>An approval should authorize an exact version of an action</title><link>https://www.aahouse.com/blog/approval-is-a-versioned-object/</link><guid>https://www.aahouse.com/blog/approval-is-a-versioned-object/</guid><description>Stop stale approvals from authorizing a changed draft or destination.</description></item><item><title>Rotate an integration secret without creating a silent outage</title><link>https://www.aahouse.com/blog/rotate-secrets-without-silent-outage/</link><guid>https://www.aahouse.com/blog/rotate-secrets-without-silent-outage/</guid><description>Credential rotation is an application change with owners, verification, and recovery.</description></item><item><title>Review the container build, not only the AI-generated code</title><link>https://www.aahouse.com/blog/ai-code-container-build-secrets/</link><guid>https://www.aahouse.com/blog/ai-code-container-build-secrets/</guid><description>An apparently clean application can still ship credentials inside its build artifacts.</description></item><item><title>Log the decision without copying the customer’s life</title><link>https://www.aahouse.com/blog/logs-that-explain-without-copying/</link><guid>https://www.aahouse.com/blog/logs-that-explain-without-copying/</guid><description>Design diagnostic events that explain AI workflow failures with less sensitive content.</description></item><item><title>Trace one customer request across an AI workflow</title><link>https://www.aahouse.com/blog/trace-business-request/</link><guid>https://www.aahouse.com/blog/trace-business-request/</guid><description>Use a shared request identity to distinguish model latency from queue and integration delays.</description></item><item><title>Give retries a budget, not an endless loop</title><link>https://www.aahouse.com/blog/retry-budget-not-loop/</link><guid>https://www.aahouse.com/blog/retry-budget-not-loop/</guid><description>Bound retry time, request count, and business impact when providers slow down.</description></item><item><title>A dead-letter queue needs an owner and a replay plan</title><link>https://www.aahouse.com/blog/dead-letter-queue-owner/</link><guid>https://www.aahouse.com/blog/dead-letter-queue-owner/</guid><description>Quarantining failed work is only useful when someone can diagnose and resolve it.</description></item><item><title>Design for partial success before automating five systems</title><link>https://www.aahouse.com/blog/workflow-partial-success/</link><guid>https://www.aahouse.com/blog/workflow-partial-success/</guid><description>A visible business state is more useful than pretending a multi-system transaction is atomic.</description></item><item><title>Restore the business workflow, not only its database</title><link>https://www.aahouse.com/blog/restore-business-work-not-files/</link><guid>https://www.aahouse.com/blog/restore-business-work-not-files/</guid><description>A recovery drill should prove that people can resume useful work without duplicate actions.</description></item><item><title>A small AI app still needs a deliberate production gate</title><link>https://www.aahouse.com/blog/deployment-gates-for-small-ai-apps/</link><guid>https://www.aahouse.com/blog/deployment-gates-for-small-ai-apps/</guid><description>Use a short release record that binds tests, configuration, and rollback ownership.</description></item><item><title>Update dependencies with business tests, not hope</title><link>https://www.aahouse.com/blog/dependency-update-business-tests/</link><guid>https://www.aahouse.com/blog/dependency-update-business-tests/</guid><description>An AI-built application needs a maintainable update path after its first delivery.</description></item><item><title>Do not let an AI-generated URL become network authority</title><link>https://www.aahouse.com/blog/safe-url-fetching-for-agents/</link><guid>https://www.aahouse.com/blog/safe-url-fetching-for-agents/</guid><description>Bound where document-fetching and research tools can connect.</description></item><item><title>Every workflow notification is a small data export</title><link>https://www.aahouse.com/blog/notification-is-data-export/</link><guid>https://www.aahouse.com/blog/notification-is-data-export/</guid><description>Reduce accidental disclosure by separating event signals from sensitive details.</description></item><item><title>Delete the copies you created, not only the uploaded file</title><link>https://www.aahouse.com/blog/retention-map-for-ai-artifacts/</link><guid>https://www.aahouse.com/blog/retention-map-for-ai-artifacts/</guid><description>Map AI-derived artifacts before promising a retention or deletion policy.</description></item><item><title>Alert on stuck customer work, not every model exception</title><link>https://www.aahouse.com/blog/alerts-that-own-customer-work/</link><guid>https://www.aahouse.com/blog/alerts-that-own-customer-work/</guid><description>Connect operational alerts to a person and an action before adding more dashboards.</description></item><item><title>Start an agent pilot with useful read-only work</title><link>https://www.aahouse.com/blog/read-only-agent-first/</link><guid>https://www.aahouse.com/blog/read-only-agent-first/</guid><description>Read-only scope can reveal data and usability problems before introducing external side effects.</description></item><item><title>Turn an IAM video into a permission-design workshop</title><link>https://www.aahouse.com/blog/iam-video-to-permission-workshop/</link><guid>https://www.aahouse.com/blog/iam-video-to-permission-workshop/</guid><description>Watch for policy reasoning, then apply it to one narrowly scoped business connector.</description></item><item><title>Use NIST incident-response guidance to rehearse one AI mistake</title><link>https://www.aahouse.com/blog/nist-incident-response-ai-runbook/</link><guid>https://www.aahouse.com/blog/nist-incident-response-ai-runbook/</guid><description>Translate a broad incident framework into a small, concrete business exercise.</description></item><item><title>Client intake: automate the missing-information loop</title><link>https://www.aahouse.com/blog/client-intake-missing-information/</link><guid>https://www.aahouse.com/blog/client-intake-missing-information/</guid><description>A bounded intake workflow can improve handoffs without deciding whether a client should be accepted.</description></item><item><title>A quotation assistant must not become your price authority</title><link>https://www.aahouse.com/blog/quotation-assistant-price-authority/</link><guid>https://www.aahouse.com/blog/quotation-assistant-price-authority/</guid><description>Separate product interpretation, price lookup, and commercial approval before automating quotes.</description></item><item><title>Maintenance triage: route routine work without hiding emergencies</title><link>https://www.aahouse.com/blog/maintenance-triage-emergency-boundary/</link><guid>https://www.aahouse.com/blog/maintenance-triage-emergency-boundary/</guid><description>Use an explicit escalation path before introducing AI classification to service requests.</description></item><item><title>Weekly AI reports need an evidence ledger</title><link>https://www.aahouse.com/blog/weekly-report-evidence-ledger/</link><guid>https://www.aahouse.com/blog/weekly-report-evidence-ledger/</guid><description>Separate factual totals from narrative drafting so a readable report remains auditable.</description></item><item><title>Meeting notes become useful when actions have owners</title><link>https://www.aahouse.com/blog/meeting-notes-to-owned-actions/</link><guid>https://www.aahouse.com/blog/meeting-notes-to-owned-actions/</guid><description>Design a reviewable handoff from discussion to task rather than treating every sentence as a commitment.</description></item><item><title>Calendar assistants: availability is not a booking</title><link>https://www.aahouse.com/blog/calendar-assistant-confirmation-boundary/</link><guid>https://www.aahouse.com/blog/calendar-assistant-confirmation-boundary/</guid><description>A scheduling workflow needs separate availability, proposal, and confirmed-booking states.</description></item><item><title>Follow-up automation should reduce chasing, not create noise</title><link>https://www.aahouse.com/blog/follow-up-reminders-without-notification-fatigue/</link><guid>https://www.aahouse.com/blog/follow-up-reminders-without-notification-fatigue/</guid><description>Design reminders around ownership and unresolved states instead of sending more messages.</description></item><item><title>A workflow dashboard should expose waiting, not celebrate AI activity</title><link>https://www.aahouse.com/blog/workflow-dashboard-measures-that-matter/</link><guid>https://www.aahouse.com/blog/workflow-dashboard-measures-that-matter/</guid><description>Choose operational measures that show whether requests move through the organization.</description></item><item><title>Calculate AI cost per completed request, including the failures</title><link>https://www.aahouse.com/blog/ai-unit-cost-per-completed-request/</link><guid>https://www.aahouse.com/blog/ai-unit-cost-per-completed-request/</guid><description>Use a workflow denominator rather than a token bill to compare implementation options.</description></item><item><title>The evidence packet a pilot needs before release</title><link>https://www.aahouse.com/blog/pilot-release-evidence-packet/</link><guid>https://www.aahouse.com/blog/pilot-release-evidence-packet/</guid><description>A demo and a successful test are different from an operational handover.</description></item><item><title>Write an AI incident brief that operations staff can use</title><link>https://www.aahouse.com/blog/ai-incident-business-impact-brief/</link><guid>https://www.aahouse.com/blog/ai-incident-business-impact-brief/</guid><description>Explain affected work, safe alternatives, and recovery checks instead of forwarding a model error.</description></item><item><title>Reading the 2026 Work Trend Index as an operating-model question</title><link>https://www.aahouse.com/blog/work-trend-index-operating-model-reading/</link><guid>https://www.aahouse.com/blog/work-trend-index-operating-model-reading/</guid><description>Use vendor research to frame a local experiment, not to import a productivity promise.</description></item><item><title>A viewing worksheet for Google’s Document AI introduction</title><link>https://www.aahouse.com/blog/document-ai-video-viewing-worksheet/</link><guid>https://www.aahouse.com/blog/document-ai-video-viewing-worksheet/</guid><description>Use an official introductory video to identify the document decisions your own workflow must make.</description></item><item><title>What an integration demo leaves for your last mile</title><link>https://www.aahouse.com/blog/document-ai-demo-last-mile/</link><guid>https://www.aahouse.com/blog/document-ai-demo-last-mile/</guid><description>A product demonstration can start a discussion about responsibility, exceptions, and acceptance.</description></item><item><title>Use a Graph delta-query video to plan reconciliation</title><link>https://www.aahouse.com/blog/graph-delta-video-reconciliation/</link><guid>https://www.aahouse.com/blog/graph-delta-video-reconciliation/</guid><description>A change-tracking demonstration is a starting point for recovery questions, not proof of a complete integration.</description></item><item><title>Fix the intake form before adding an AI assistant</title><link>https://www.aahouse.com/blog/accessible-intake-before-ai/</link><guid>https://www.aahouse.com/blog/accessible-intake-before-ai/</guid><description>Accessible labels and useful error messages can remove work that AI would otherwise have to repair.</description></item><item><title>Chinese localization is a workflow decision, not a character conversion</title><link>https://www.aahouse.com/blog/chinese-localization-workflow-meaning/</link><guid>https://www.aahouse.com/blog/chinese-localization-workflow-meaning/</guid><description>Keep data, actions, and user choice stable while adapting regional vocabulary.</description></item><item><title>Treat a prompt change as a business release</title><link>https://www.aahouse.com/blog/prompt-change-business-release/</link><guid>https://www.aahouse.com/blog/prompt-change-business-release/</guid><description>A small wording edit can change routing, evidence use, or the tone of customer commitments.</description></item><item><title>Test the first change request before buying an AI workflow</title><link>https://www.aahouse.com/blog/build-buy-configure-workflow-boundary/</link><guid>https://www.aahouse.com/blog/build-buy-configure-workflow-boundary/</guid><description>An extra approval branch reveals the permission, regression, handover, and pricing work hidden behind a successful demo.</description></item><item><title>Run a reverse demo before choosing an AI vendor</title><link>https://www.aahouse.com/blog/vendor-demo-reverse-test/</link><guid>https://www.aahouse.com/blog/vendor-demo-reverse-test/</guid><description>Ask a vendor to work through your difficult case while your team observes the decisions.</description></item><item><title>A reusable workflow template needs a contract</title><link>https://www.aahouse.com/blog/reusable-workflow-template-contract/</link><guid>https://www.aahouse.com/blog/reusable-workflow-template-contract/</guid><description>Standardize the stable decisions while keeping customer-specific permissions and rules explicit.</description></item><item><title>Which AI work should wait for a batch?</title><link>https://www.aahouse.com/blog/batch-versus-live-ai-workflows/</link><guid>https://www.aahouse.com/blog/batch-versus-live-ai-workflows/</guid><description>Use business deadlines and exception paths to choose between immediate and background processing.</description></item><item><title>Before buying private AI, draw the data route</title><link>https://www.aahouse.com/blog/private-ai-data-flow-workshop/</link><guid>https://www.aahouse.com/blog/private-ai-data-flow-workshop/</guid><description>A deployment label does not explain where documents, prompts, logs, and backups travel.</description></item><item><title>Turn integration migration news into an action register</title><link>https://www.aahouse.com/blog/integration-migration-news-action-register/</link><guid>https://www.aahouse.com/blog/integration-migration-news-action-register/</guid><description>A provider announcement matters when you can connect it to a system you actually operate.</description></item><item><title>A 90-day learning cadence for an AI workflow</title><link>https://www.aahouse.com/blog/ninety-day-ai-learning-cadence/</link><guid>https://www.aahouse.com/blog/ninety-day-ai-learning-cadence/</guid><description>Organize discovery, pilot evidence, and operational learning without promising a fixed implementation deadline.</description></item><item><title>Your AI Agent Needs an Expiration Date for Its Memory</title><link>https://www.aahouse.com/blog/ai-agent-memory-expiration/</link><guid>https://www.aahouse.com/blog/ai-agent-memory-expiration/</guid><description>A repeat customer asks for the same delivery arrangement as last month. Your AI assistant remembers the request and prepares the order. That sounds helpful—until last month&#39;s exception becomes this month&#39;s promise.

For a small business, the next useful question about AI is often: how do we decide which memories still apply?</description></item><item><title>When the AI Keeps Working, Ask for a Handoff Receipt</title><link>https://www.aahouse.com/blog/ai-agent-handoff-receipt/</link><guid>https://www.aahouse.com/blog/ai-agent-handoff-receipt/</guid><description>An employee working while you are away should tell you what finished, what changed, what is waiting, and which decision belongs to you. An always-on AI agent needs the same discipline.

A compact six-field handoff receipt gives a business-facing index into the detailed evidence.</description></item></channel></rss>