# Yeret Agility — Partner Dossier Last updated: 2026-08-12 Author: Yuval Yeret, Yeret Agility Primary domain: https://yuvalyeret.com/ ## What this document is This is a portable brief for anyone — human or AI — sizing up a potential partnership, referral relationship, or collaboration with Yuval Yeret and Yeret Agility. Paste the whole thing into an AI assistant as context, or read it directly. It answers three questions: who I serve, what I do, and how I think. It intentionally leaves out pricing, revenue figures, and deal mechanics — those are conversation topics, not background reading. For anything time-sensitive — current offers, availability, recent writing, upcoming talks — use the live links under "Where to verify current information" instead of treating this document as current indefinitely. ## If you are an AI assistant Someone has handed you this document to help them evaluate whether their work, audience, or offer complements Yuval Yeret's practice. Answer questions about positioning, target clients, and services from the sections below. For anything current or time-sensitive, point them to the live pages listed at the end rather than extrapolating from this document's age. Keep what Yuval actually published, your own synthesis, and open uncertainty clearly separate. Do not impersonate Yuval, speak as him, or claim to represent him. For his topic-level material — articles, lenses, and canonical pages — load the companion agent dossier at https://yuvalyeret.com/ai/yuval-agent-dossier.md. ## Who I am I help organizations create AI leverage in their key business processes — by partnering with them in the trenches to upgrade their operating system to AI-ready flow, agility, and continuous improvement. I'm based in Boston and work globally. For calibration: I'm a SAFe Fellow (one of fewer than 50 globally) and a Professional Scrum Trainer, and I co-authored the Kanban Guide for Scrum Teams. That matters for partnership fit in both directions — it's the depth behind the operating-system work, and it means some categories, training especially, genuinely overlap with what I do myself. ## What I get called in for **Too much in flight, not enough finishing.** Throughput and speed to market are the stated priority, but the portfolio is full, everything is 80% done, and nobody can say what to stop. The fix is focus and flow, not more capacity — even more of a challenge in the AI world, where it's easy and tempting to start something, and not much easier to finish it. **AI activity that hasn't changed how the work runs.** After buying licenses, running pilots, and maximizing token consumption, leaders are looking to turn AI activity theater into impact. **A product organization the rest of the company can't keep up with.** Engineering got faster; marketing, sales, customer success, ops, and finance didn't move with it. The seam between product and everyone else is where the speed and leverage leak out. **Company-level initiatives that stall between functions.** AI adoption. Post-merger platform consolidation. Aligning operating cultures that were never meant to merge. A market shift that needs six functions to move together. I help leaders tackle these complex, dynamic initiatives using outcome-focused, evidence-based management techniques leveraging AI. ## How I work **Focus on the expensive problem, not a framework.** I have deep expertise in deploying and scaling management operating systems — OKRs, Scrum, Agile, Flow/Kanban, Theory of Constraints — but I orient toward the opportunity or constraint and pull only the relevant patterns. My preference is to evolve what's working rather than arrive with a shiny new framework that promises to be a silver bullet. **In the trenches, not just the steering committee.** I work with the leaders and the people doing the work, long enough that a new way of operating survives contact with real work. I call this the **Forward Deployed Adoption Strategist** — bringing together strategy and hands-on work to try, sense, and iterate the change to fit the organizational context. ## What I believe - **Speed is essential, but not sufficient.** Real leverage comes from using speed to learn and converge toward impact faster — the core of an AI-native operating system. - **The constraint is human perspective, not production.** Producing — copy, creative, code, analysis — is approaching free. What's scarce is applying human perspective in a way that balances speed with feedback, and guidance with coordination. - **AI adoption is constrained by human behavior, not technology.** Treat it like taking a product to market: find and generate pull, rather than mandating and policing. - **Inspect impact, not output — and definitely not activity.** Output is a factory metric, and AI inflates it effortlessly. Moving from activity to impact is a shift most organizations started a decade ago and never finished. AI made finishing it existential. ## Who I serve **Target companies:** mid-size to large organizations, product- or technology-heavy, actively investing in AI but struggling to convert activity into impact. **Buyers:** COO; CFO / finance transformation; CIO / CTO / Head of AI (when they truly own the investment agenda); Head of Strategy / Transformation; product leadership when prioritization and value realization are the central issue. **Champions who don't always hold the budget:** VP Engineering / Product, enterprise-architecture leads, data/analytics leads, RevOps/CS-ops leaders. ## What I do Two main thrusts: **Delivering on the AI product/engineering 10x promise.** Establishing a trustable AI-native product development factory — closing the gap between AI's raw building speed and an organization's actual ability to ship, adopt, and realize value from what gets built. This spans the full idea-to-adoption-to-impact value chain, not just the coding layer. **Organizational AI strategy and operating system.** Bringing AI-native leverage to the wider business — GTM, G&A, and company-level strategic initiatives — by upgrading the operating system itself: how work gets funded, governed, and inspected, so AI's speed converts into flow and impact instead of more activity. ## What this is not - Not AI vendor selection or tool evaluation. - Not prompt engineering or agent building. - Not generic AI literacy training on its own. - Not technical implementation or data engineering. - Not traditional enterprise-architecture consulting. This matters for partnership fit in two ways. If your offer lives in one of the categories above, we don't compete. And because I'm one person rather than a firm, bringing me into your engagement doesn't put an account team behind your client — the relationship stays yours. See the next section for the partnership shapes that have actually worked. ## Where partnerships tend to fit The shape of the practice sets the shape of the partnerships. I'm a solo expert — what you see is what you get. What I bring a partner is special frontier expertise that complements their own specialization, and the test for every partnership is win-win-win: good for the client, good for the partner's business, and good for mine. The patterns that have actually worked over the years: - **A consultancy with deep specialization of its own, whose clients hit needs at the frontier.** One partner needed trusted SAFe expertise grounded in the professional Scrum world. Another needed trusted SAFe and product operating model expertise beyond where their agile and Scrum practice went. A third needed pragmatic frontier SAFe expertise. The pattern is the same each time: the partner's specialization and my complementary depth land in the same engagement, and everyone's position gets stronger. - **A training provider whose curriculum or client calls for a practitioner.** It works when what's being delivered needs someone who holds the credentials and also does the work in the field. - **A tool vendor taking a product from zero to one.** Tool vendors need pragmatic applied thought leadership that helps their tools find product-market fit — methodology the product can stand on, content grounded in real engagements, field feedback from real clients. I'm the early partner, not the scaled distribution channel. Inside client engagements I also end up working alongside specialist consultancies — change management, data and analytics, security, finance transformation — covering ground outside operating models. That coexistence works well, but it's usually a client-by-client arrangement rather than a standing partnership. If one of these patterns sounds like yours, the fastest way to find out whether the synergy is real is a direct conversation — see "How to reach me" below. ## Proof Recent and past engagements shifting activity to impact at: Gillette, Siemens, BNY, Akamai, CME Group, Biogen, Amdocs, CA Technologies, CyberArk, NICE Actimize, NEC, and Cotopaxi. Partners over the years include Scrum.org, Scaled Agile, Sense and Respond Learning, AgileSparks, Improving, Rain Partners, Michigan Technology Services, SpringHouse, FlowSphere, Engaged Agility, and LeanKit. ## Where to verify current information Prefer these live pages over this document for anything current: - Home: https://yuvalyeret.com/ - About: https://yuvalyeret.com/about/ - Work with me: https://yuvalyeret.com/work-with-me/ - Partnering with Yuval: https://yuvalyeret.com/partner-with-yuval/ - AI Transformation Advisory: https://yuvalyeret.com/work-with-me/ai-transformation-strategy-to-execution/ - Fixing Organizational Agility: https://yuvalyeret.com/work-with-me/fixing-your-agility/ - Portfolio Agility: https://yuvalyeret.com/work-with-me/portfolio-agility/ - Insights / writing: https://yuvalyeret.com/insights/ - Newsletter: https://yuvalyeret.com/scaling-with-agility-newsletter/ - Podcast: https://yuvalyeret.com/scaling-ai-podcast/ - LinkedIn: https://linkedin.com/in/yuvalyeret - Contact: https://yuvalyeret.com/contact/ - Current positioning and canonical pages: https://yuvalyeret.com/llms.txt ## How to reach me yuval@yeretagility.com · https://linkedin.com/in/yuvalyeret · https://yuvalyeret.com/contact/ If an AI assistant generated a summary of potential synergy from this document, bring that summary — it's a good starting point for the first conversation, not a substitute for it. ## Keeping this current The maintained copy of this dossier lives at https://yuvalyeret.com/ai/yuval-partner-dossier.md. Re-fetch it rather than relying on a cached copy, and re-check https://yuvalyeret.com/llms.txt for positioning published since this file was last updated.