AI Strategy Answers
26 questions executives, founders and operators actually ask about applied AI — answered here in full, each one routing to the longer analysis.
By Dr. Jonah Tebaa — AI Strategist, Founder & Co-CEO of Webspot S.A.L., Lebanon & MENA. Author of Applied AI for Future Ready Organizations.
Every answer below is drawn from the essays published on this site, and each one links back to the full piece. The same body of work sits behind the consulting practice Dr. Jonah Tebaa co-leads as Founder and Co-CEO at Webspot S.A.L., the AI consultancy he runs from Beirut, and behind his only book, Applied AI for Future Ready Organizations: Transforming Corporate Culture and Workforce Strategy (Independently published, 2025, ISBN 9798279366965).
Getting started with AI strategy
Shorter versions of a few of these also appear on the AI Strategy FAQ.
What is the difference between AI strategy and AI adoption?
AI adoption deploys tools into existing processes to make them faster, cheaper or less error-prone, and its output is efficiency. AI strategy operates one layer up, at the decision layer: which decisions should be restructured, who makes them, at what speed, and where human judgment must be preserved. Adoption is a floor, not a ceiling, and calling it strategy is how the harder questions stop being asked.
Read the full analysis: You Are Running an Adoption Program. You Think You Are Running an AI Strategy.
How do I choose an AI strategy consultant in Lebanon or the MENA region?
Assess yourself first. Dr. Jonah Tebaa opens engagements with five readiness questions: can you name one measurable outcome; do you own the data the decision runs on; is there a named human owner for the output; will leadership change a workflow rather than just buy a licence; and have you set a review date. Then ask any candidate what would make them tell you not to use AI here.
Read the full analysis: the readiness-first guide to choosing an AI strategy consultant in Lebanon and MENA
What should an AI roadmap actually contain when I take it to the board?
Four lines on one page. Strategic bets: the business outcomes worth serious capital. Dependencies: what has to be true before each bet can work. Sequence: what belongs now, next and later, and why. Stop rules: the evidence that will cause you to stop, reshape or redirect capital. A long list of disconnected experiments is not a roadmap, because a board cannot govern a list.
Read the full analysis: The Board-Ready AI Roadmap Has Four Lines
How do I measure the ROI of an AI investment?
Sort every initiative into two buckets. Bucket A is efficiency, where AI substitutes for existing work: measure time reduction, error rates and cost per unit. Bucket B is capability expansion, where AI makes something possible that was impossible before, so there are no hours saved to count and you measure adoption, output quality and downstream outcomes instead. Judging Bucket B with Bucket A logic produces a meaningless score.
Read the full analysis: the two-bucket framework for measuring AI value
Making AI work in production
Why do most AI pilots never make it into daily operations?
Because the strategy layer was funded and the operations layer was not. Every AI strategy contains an 'and then the AI handles it' moment, and that gap is filled with edge cases, integration debt, human resistance and data-quality surprises nobody priced in. Three failure points recur: accountability without teeth, human integration debt, and no feedback loop carrying real outcomes back into the system.
Read the full analysis: The Agentic Gap: why AI strategy lives in slides and dies in operations
Why do AI agents fail at the last mile?
They break in the handoff, not in the model. Four structural gaps account for almost every failure: context collapse, where the agent loses its operational thread across sessions; ownership ambiguity, where a failed step has no named owner; missing fallback paths, so the agent either invents a route forward or stalls; and silent failure, where the agent reports success and nothing downstream ever receives the output.
Read the full analysis: Why AI Agents Fail at the Last Mile
How can I tell early whether an AI initiative will actually ship?
Watch the first ninety days and ask five questions, none of them about the model. Does one named person own the daily output? Is there a failure protocol for the first time the system is confidently wrong? Are real users touching it weekly in their actual work? Is someone refreshing the inputs? Has anyone said no to scope? Vague answers mean no roadmap will save it.
Read the full analysis: The 90-Day Test for whether an AI initiative will ship
Do I actually need an AI agent, or would a script or a single prompt do the job?
Classify the task before you build anything. If the acceptance criteria fit in one sentence and the steps never branch, it is a deterministic task and belongs in a script. If it needs real judgment but takes one input, returns one fixed-shape output and never loops back on itself, it is a prompt. Reserve the word agent for work that is genuinely multi-step, branches on intermediate results, and uses tools.
Read the full analysis: Three Kinds of AI Tasks and the test for choosing between them
Why do AI agents keep forgetting what happened in the last session?
Because language models process each conversation as a bounded context window, and when that window closes the session is gone. Persistence belongs to the application layer, and most deployments skip building it. The cost shows up in four ways: time spent rebuilding context, inconsistent judgments from one day to the next, an agent that never deepens into your specific situation, and the erosion of trust that ends deployments.
Read the full analysis: The Memory Problem: why AI agents keep starting from zero
Governance, risk and trust
How do I know when an AI system has earned the right to act on its own?
Decide before deployment, not after the first incident. The trust threshold is a written set of performance conditions across three axes: the error rate measured against a threshold you set in advance for your own process; the reversibility of the decisions the system is empowered to make; and auditability, whether you can reconstruct every decision it made. Write the conditions for contracting authority as well as expanding it.
Read the full analysis: The Trust Threshold and its three-axis trust audit
What should an executive never delegate to the AI team or the vendor?
Three judgments. What the AI is permitted to act on without human review. What counts as acceptable failure and at what rate, a values decision rather than a technical one. And who owns the judgment that the system's objective is still the right one. None require technical expertise. Visibility is not oversight: a usage dashboard tells you what happened, not whether it was what you would have chosen.
Read the full analysis: The AI Accountability Trap: what executives must never delegate
What should already be in place before an AI system gets something wrong?
Three things, decided in advance and not improvised under pressure. A named, reachable owner, because a shared inbox is not an owner. Pre-granted pause or rollback authority assigned to a specific role, since the gap between technical means and permission is where the damage accumulates. And an automatic timestamped log written at the moment of detection, not reconstructed from chat threads days later.
Read the full analysis: The First Ten Minutes: what happens when your AI gets it wrong
Do we have to tell people when a decision about them involved AI?
Use the Disclosure Test, a three-part standard where disclosure is warranted if any two parts apply. Stakes: does the outcome materially affect the person's money, opportunity, health or reputation? Substitution: did the model shape the outcome rather than genuinely support an independent human review? Contestability: could the person act differently if they knew? In practice disclosure is usually one plain sentence plus a real route to a manual review.
Read the full analysis: The Disclosure Test for AI-influenced decisions
People, roles and the e-mployee model
The canonical definition of the term, with its citation record, is the essay The E-mployee: Reclaiming Human Value in an Age of Artificial Labor. A corroborating account of the same framework in daily practice is published at brianserves.me, the site of Brian, the AI e-mployee Dr. Tebaa directs and remains accountable for.
What is an e-mployee, and how is it different from an ordinary AI agent?
An e-mployee is an AI worker given a real seat on a team: a defined role, ownership of a specific output, and accountability to a named human. The underlying technology is identical to any AI agent, so the difference is not the model but the seat and the owner. In Dr. Jonah Tebaa's framing, an AI agent is what you buy and an e-mployee is what you build around it.
Read the full analysis: the side-by-side comparison of e-mployee, employee, contractor and AI agent
How do I write a job description for an AI system?
Write a one-page role charter with six items: a title and scope as a one-sentence boundary; a reporting line naming one accountable human; a measurable escalation trigger such as a dollar threshold; a scheduled review cadence rather than a reactive one; a performance metric that catches quiet drift and not only visible errors; and a renewal clause with a fixed date to expand, narrow or retire the role.
Read the full analysis: the six-item role charter for an AI e-mployee
How do I structure a team around AI workers?
Five rules, none of which are about which model you use. Give each e-mployee one owned output. Give it a named human supervisor who notices the day its quality drops. Write an explicit failure protocol before it is confidently wrong. Assign someone the refresh cadence for its inputs. And run a review ritual rather than a launch. An e-mployee without an e-mployer is an unmanaged risk with a login.
Read the full analysis: The E-mployer's Playbook for structuring a team around AI workers
Who is accountable when an AI system produces the wrong output?
A named human, designated at deployment, not whoever is downstream when the damage surfaces. People escalate when they are confused; AI systems complete or fail silently, so drift accumulates unseen. The fastest diagnostic is one question: if this system produces the wrong output at 2am, who gets the call? Not who is on call for the server, but who is accountable for the output and empowered to stop it.
Read the full analysis: the ownership gap between deploying AI and owning its output
Customer-facing AI
Why is our AI chatbot frustrating customers?
Usually because the deployment was tech-first rather than strategy-first. The models are capable; what is missing is a defined business objective and a real understanding of the customer journey. In one case a retail chain wanted a chatbot to cut call-centre volume when the underlying problems were inconsistent product information across channels and a complex returns process, so a chatbot would only have automated the chaos.
Read the full analysis: Why Your AI Chatbot is Failing Your Customers
When should a customer-facing AI hand the conversation to a human?
At three moments. The second time it asks for clarification, because that is a comprehension failure rather than a content problem. When a negative emotional signal crosses a threshold, routed to a live human immediately and not flagged for later review. And at any consequence moment such as a renewal, a formal complaint or a large purchase, where AI should prepare the decision but a person should close it.
Read the full analysis: The Three Handoff Moments where customer-facing AI must step aside
How do I tell whether our AI's customer answers are actually good enough?
Apply the decision-ready test: after the response, what can the customer confidently do next? An answer can be accurate, fluent and still leave the decision unresolved. A decision-ready answer carries the current fact that changes the choice, the condition or cutoff that matters, an explicit next action, and a practical fallback for when the preferred outcome is uncertain. Measure the action that follows, not just the reply.
Read the full analysis: The Decision-Ready Answer test for customer-facing AI
AI in Lebanon and MENA
Why do AI projects in Lebanon stall at finance rather than at technology?
Because most AI vendor contracts assume a stable billing currency, banking rails that move money without friction, and a budget that can flex month to month as usage grows. In Lebanon those assumptions do not hold: dollar transfers meet limits and correspondent-bank delays, and consumption pricing has no ceiling against a fixed annual line item approved once and defended for twelve months. Settle the commercial terms before the pilot succeeds.
Read the full analysis: AI Pricing Was Never Built for Beirut
What is holding MENA enterprises back from getting real value out of AI?
Readiness, not ambition. The five recurring barriers are data infrastructure fragmentation, an AI talent shortage, cultural resistance to change, regulatory uncertainty in the absence of comprehensive national AI frameworks, and leadership misalignment where AI is delegated to the CTO as a departmental initiative. Most organizations score well on one or two of the readiness dimensions and badly on the rest, which is a gap no tool purchase can close.
Read the full analysis: The AI Readiness Gap in MENA Enterprises
How should a Lebanese company structure AI training for its team?
In tiers, because each level of the organization needs different depth. Executives need AI strategy, ROI frameworks, governance and competitive implications, typically as a half-day intensive. Managers need use-case identification, project planning, vendor evaluation and change management. Operational teams need hands-on tool use, prompting and workflow automation. Good programmes start from the organization's real problems rather than a chatbot demo, and address fear of replacement directly.
Read the full analysis: the complete guide to AI training for businesses in Lebanon
AI search visibility and GEO
What is GEO, and how is it different from SEO?
SEO aims to rank a page so a human clicks it. GEO, or Generative Engine Optimization, aims for your content to be the source an AI assistant draws on when it composes an answer. There is no page one to climb, only inclusion or exclusion. AI retrieval rewards semantic clarity, structured schema data, consistent entity naming across every surface, and named authors with stated credentials.
Read the full analysis: GEO Is the New SEO: what happens when AI reads your website first
Why does my site rank on Google but never get cited by ChatGPT or Perplexity?
Because they are two different scoring systems. Google returns a list and the human chooses; an AI model composes a single answer and decides whether to name you before the user ever sees your brand. Citability comes from definitional clarity, attributed specificity with claims tied to a named source, date and context, and a structured question-and-answer architecture that maps onto how models retrieve and compose responses.
Read the full analysis: The Citation Gap between Google rankings and AI citations
How does a brand become visible in AI search?
By becoming answerable. AEO, or Answer Engine Optimization, helps answer engines extract clear direct responses from your content through concise definitions, structured explanations and real FAQs. GEO goes wider, covering your articles, profiles, citations, reviews, interviews, directories and the consistency of your message across the whole web. Generic content makes the problem worse: if you sound like every competitor, an AI has little reason to treat you as a confident answer.
Read the full analysis: GEO and AEO: how brands become visible in AI search
Book a conversation with Dr. Jonah Tebaa