Design for a world that doesn’t stand still.

We turn complexity into clarity, creating intelligent experiences that help people understand what matters, decide what comes next and keep the world’s most essential industries moving.

One system. Every IFS experience.

The foundations, components and patterns behind our products — helping teams move faster, stay consistent and turn shared foundations into great experiences.

How we think about design at IFS

The beliefs that guide the decisions we make — from the smallest interaction to entire product experiences. A shared foundation for making things useful, coherent and unmistakably IFS.

  • Clarity

    Make the complex legible.

    We cannot simplify a plant, a fleet, or a supply chain. We can make it understandable. Order the information, and show what the decision needs rather than everything the system holds.

  • Context

    Design for the shift, not the demo.

    The same job looks different in a maintenance bay, a vehicle cab, and a planning office. Role, task, and environment shape the interface, not personal preference.

  • Consequence

    Design the failure first.

    A missed inspection or a wrongly scheduled technician costs real money, and sometimes safety. Where being wrong is expensive, design the wrong path before the happy one.

  • Trust

    Show the working.

    When the software recommends or decides, it explains itself. State confidence honestly, keep actions reversible where you can, and never leave someone unable to say why.

  • Consistency

    One product, not forty.

    A customer moving between our applications should not have to learn our org chart. The design system is how we keep that promise, and it only holds if every squad uses it.

  • Evidence

    Decide with customers.

    Every significant decision traces back to something a customer said, did, or struggled with. Until it has been tested with them, a strong opinion is still a hypothesis.

  • Craft

    The detail is the product.

    In enterprise software, the table, the empty state, and the error message are the work, not decoration around it. Craft is doing them properly even when nobody outside the team will ever notice.

  • Agency

    Know whose decision it is.

    A tool does exactly what’s asked of it. An agent acts toward a goal on someone’s behalf, inside limits we set on purpose. Either way, the person stays in charge: they can direct it, interrupt it, and switch it off, and the interface has to make all three obvious, not just possible.

What we’re learning along the way

Ideas, observations and lessons from the people designing IFS products. A place to share what worked, what didn’t, and how our thinking continues to evolve.

  • An isometric drawing: tiles for the Design, Product and Engineering teams raised over six for the site's sections, Foundations to About, joined by lines.

    Community

    One home for how IFS designs: our standards, our thinking and the tools we use every day.

    Design Team

Everything you need to make something great

Tools, templates, assets and guidance for putting IFS design into practice. Less searching, more making.

  • The methodology behind the toolkit: three pillars, four phases with their milestones and outcomes.

    Slides template
  • One worksheet, revisited four times across the discovery with increasing fidelity. Not four separate tools.

    FigJam board
  • Four ready-to-run warm-ups, so the first time somebody speaks is not also the first time they are asked something hard.

    FigJam board
  • A one-page brief filled in with your sponsors before kickoff, covering context, users, goals, outcomes and who decides.

    FigJam board
  • Four questions that check whether a project is actually ready: what we have, what we are missing, what could block us, what we can learn from.

    FigJam board