Craig Errey

Solve Group Pty Ltd

Craig is an organisational psychologist, business architect and UI/UX/CX designer specialising in connecting people, work, and technology. Craig holds a Masters in Applied Psychology from UNSW and is a Registered Psychologist in Australia.

For 30 years, Craig Errey has worked on the requirements and user interface design for some of the largest organisations in Australia including Commonwealth Bank, CUA, Telstra, Qantas, NSW Department of Education, NSW Department of Industry, ASIC, Australian Parliament House, ANZ Bank, and Tourism Australia. Craig has designed apps used by millions of people, every day.

His insight into technology in the workplace has been called on by media outlets including the Sydney Morning Herald, The Australian, 2UE and ABC Radio National. Craig also gave a TEDx talk on the four-day week at full pay.

Presentation: A standard process and visual blueprint for the design of complex software systems

Software engineering is the only one of the five main engineering disciplines that does not have a standardised process and visual blueprint for its products. Without this, we have to rely on written requirements. But, have you ever heard an engineer say:

You know, a thousand words really is much better than a picture…

Writing is the most popular approach to documenting requirements, but they’re incomplete, ambiguous and open to interpretation. Would you ever describe your new building, or an electronic device or a just invented machine in words alone?

The result is a low, persistent 29% success rate across all enterprise IT projects (Standish Chaos Reports). Meanwhile, 22% fail outright. Ouch! Imagine if 22% of civil engineering projects failed? Or if 22% of chemicals produced were thrown out? So why do we keep using written requirements?

This talk introduces a standard process and visual blueprint for the design of complex software systems. It is to software engineering what architecture is to civil engineering. It works with Agile, waterfall, or any other development methodology, as well as any platform, technology, or framework. You can also use it if you want to buy or build your solution.

You’ll learn how to create simple, precise, and comprehensive visual models based on a foundation of organisational psychology. You’ll also learn how to connect the often-disconnected activities of requirements, user interface design, system architecture, and development.

And you’ll learn how to create and maintain conceptual integrity, while putting a stop to continuously changing requirements.

Together, this creates a common language between business and IT that’s fast enough to use in workshops instead of post-it notes.