About

Why we wrote these down

We kept watching the same failure repeat. Organizations adopt AI, execution speeds up, and the unclear parts (who owns what, what was decided, what the product should actually feel like) start breaking faster than anyone can fix them.

None of the ideas here are new on their own. Agile, team health research, systems thinking and product design all got there first. What we found missing was a single, explicit stack that holds them together and says plainly what to prioritize when speed and clarity pull in different directions.

So we wrote four manifestos, one for each layer, in the format the Agile Manifesto made familiar: a short preamble, a handful of value trade-offs, and principles you can hold work against.

Using the manifestos

Share them, quote them, print them for a workshop, adapt them for your own team. We only ask that you credit the source and link back to the original. Every manifesto has a PDF version for exactly that purpose.

Disagree with something?

Good. These documents get better when they get argued with. Write to us at hello@unambiguous.build.

Who we are

The people behind Unambiguous

Together we form the product trio: product, experience and engineering working as one to build systems people can rely on when it matters. The manifestos live here. Their applied practice lives at Unambiguous Build.

  • Harkirat Singh

    Product Leader

    Rotterdam, Netherlands

    LinkedInprofile of Harkirat Singh (opens in a new tab)

    AI-Native Platforms · Experience-First Systems · Agentic & Multimodal Workflows

    • Product Leadership
    • Agentic Workflows
    • Orchestration
    • Multi-tenant Platforms

    Harkirat builds AI-native product platforms for complex, real-world systems, focusing on how systems behave under pressure: when decisions matter, when things fail, and when users need clarity, control, and trust.

    He has led platform transformations that reduced development cycles by over 80%, scaled multi-tenant systems across global enterprise clients, and introduced AI-driven workflows grounded in real operational constraints. His work led to the Cascading Experiences Model, aligning platform, enablement, product, interaction, and interface design into one coherent system.

  • Katrien Meijdam

    Experiences (CX/UX) Leader

    Rotterdam, Netherlands

    LinkedInprofile of Katrien Meijdam (opens in a new tab)

    Turning complex problems into clear product decisions

    • Product Strategy
    • Product Discovery
    • Design Sprints
    • Facilitation

    Katrien helps teams figure out what's worth building before they build it. Her work sits at the intersection of UX and product: understanding users and their context, making sense of complex problems, and bringing product, design, and engineering together around what to build and why.

    She is most at home in the messy part of product development: talking to customers, mapping systems and journeys, prototyping ideas, and challenging assumptions until there is enough evidence to decide. Lately she has been exploring how AI changes both product discovery and the products we build.

  • Vincent van Gameren

    Engineering Leader

    Geldermalsen, Netherlands

    LinkedInprofile of Vincent van Gameren (opens in a new tab)

    Applied Innovation & Engineering Culture · Product-Driven Development

    • Agentic AI Development
    • Model Context Protocol
    • System Architecture
    • Team Leadership

    With 20+ years in software development, Vincent works at the intersection of engineering, product, and innovation: shaping technical direction, guiding architectural decisions, and strengthening engineering culture with a strong bias toward long-term quality and predictable outcomes.

    He approaches AI as a capability that must be applied deliberately and understood deeply: it should amplify engineers, not replace their thinking or accountability. Development, in his view, should be driven by product intent and user experience, not by the constraints of the current technical setup.