<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=4958233&amp;fmt=gif">
RSS Feed

Next Gen Insights | Graeme Fordyce |
13 August 2019


When a large company transforms to a platform-based infrastructure, the intent is shipping more product to a growing user base more quickly and with higher quality. Of course, organisational theory in and of itself can’t magically affect that set of outcomes from the top. A streamlined chart of people and processes looks great and is meant to make sense of complexity, but what is happening with products on the ground needs to be running effectively.

The broader platform model is predicated on independent systems that can more easily share data, components, and experiences so that the technical framework can be used to build multiple products. If the business is scaling and more product is shipping more frequently, there’s likely more interrelated content, functionality, and customer interaction to understand from a high level.

The flexibility on offer from a platform-driven approach can set up a business for success, but without good old-fashioned human communication, there’s arguably more potential for complexification in the system as initiatives are tried, as products proliferate and grow. At both the strategic and tactical levels, some due-diligence aspects of product management can help keep chaos at bay. Getting the help of a large, established technology partner that’s familiar with the ins and outs of the platform play can help companies organise thoughtful, streamlined processes, and avoid a lot of the grind of transforming.


The role of a Platform Product Manager and why it’s a good idea

One seduction of acting like a tech company is that things will start to move really quickly. It’s all very exciting and we’re shipping and adding value and there’s no time to produce and pore over reams of documentation. And it’s hard to take a moment to look at all of the different pieces and collect them into shape. Not doing so, however, exposes the company to risk because problems will proliferate in at least a direct relationship to expanding interdependencies and relationships between products on the platform.

When this is happening, it’s important to have people with particular skillsets there to act as the connective tissue among teams and streams. These are the Platform Product Managers (PPMs), customer-centric, technically-sound thinkers dutybound to understand the wide-ranging relationships and interdependencies created by a platform-based organisation. This is a somewhat different animal than a Platform Manger, who tends to be CS/Engineering-educated and very focused on technical matters.

PPMs are there as a pivot between executives and the traditional hyper-user-focused Product Managers and help manage across the business from stakeholders to UXers to developers. PPMs cast their vision both tactically for immediate needs and long-term in the roadmap for users. In a large organisation that already has the complexity of needing platform transformation, it’s useful to differentiate the PPM and PM so that the latter doesn’t get pulled too much in one direction among technical considerations, business needs, and user needs, and also so that nobody simply gets stretched too thinly in the difficult process of evolution.

Within the business they must see in both directions: inform executive planning by pushing upwards what the PMs know about users and jobs-to-be-solved, and simultaneously make sense of the shared content and functionality available so that PMs can maximise the potential of the platform in service of the customer base. This is a role that can prioritise work based on platform strengths and capabilities and help collect apparently disparate business initiatives into shape for maximum design/development efficiency and brand effect.


Documentation is a good thing; writing things down is critical to build collective understanding.

Many clients we interact with won’t have traditional PMs and UXers, and as a consequence our design teams and by extension dev teams will be intaking work requests with less-than-optimal detail, guidance, and justification. Too often, well-intentioned, smart, motivated cross-functional teams don’t manage to communicate effectively. How does the PM, the prime mover and gravitational centre of a product/feature/initiative, prevent lapses, gaps, and errors? Once we get down to the executional level, we have to be extra careful to keep order to the dynamic and complex in a scaling platform environment.

“- I’d like to get some use cases written up prior to UX launching into the designs, spec out how the features are supposed to work…

- Specifications are kind of old-world thinking. We’re working in agile.”

In this context, agile is the word on the tip of everyone’s tongue. Agile is deservedly the dominant paradigm, but like any popular idea, is prone to stereotyping. The relentless cadence of working in agile requires terrific discipline and structure but ironically the term is often deployed to avoid process and documentation. This might sound a little like waterfall territory, but it’s more a reaction to a common over-rotation into a more caricatural version of agile that seems to have arisen from the hyper-pressure to ship and the way that ideas frequently extremify when they make that mysterious cultural move from sound principles into dogma.

Platform transformations don’t work magically by themselves—they lend the potential for improving aspects of work and workflow for organisations and people. The details, what features actually get built and why, require even more diligence and attention in the platform model because visibility and access are actually better. Duty and deliberateness are heightened, and those are attended to by solid product management principles that often get left behind by pat and facile interpretations of agile. Even in the start-up space, which feels innovative and adaptive and fast-moving to businesses that are emerging from a more traditional operating model, it’s a frequent pitfall. As a general principle, when one part of the business is clarified, simplified, streamlined into logical services, the alignment and fluidity of communication among those groups has to follow suit.

For the tech and business sides to move together quickly and effectively and prevent problematically incomplete work slipping through to the consumer, there must be a requisite understanding of how vision and tactics align around a consumer need. There must be enough detail on record to make sure that a project is initialised adequately and has real substance rather than only a sense of direction. There’s a great, old-fashioned way to achieve this – writing things down. This is where the PM, the ‘CEO’ of the product/feature, needs to be strong, clear, and articulate… and document hypotheses (in the form of sufficient product requirements) from cloud to fish level.

“- There are lots of UX bugs that need to be addressed…

- We’re going for an MVP, so we’ll have to fix them later. We need to be agile.”

Nobody wants to drown in documentation. A thousand clam-level use-cases will drive anyone crazy. But the consequence of abused principles dressed up as agile often results in nothing, or almost nothing, getting documented. It happens all the time when teams are trying to respond to the pressure to deliver move quickly. Preventable mistakes get through, things that require time to go back and clean up later, from the flying-by-the-seat-of-your-pants mentality. The obvious counter is that the agile model accounts for and responds to this pain, which is true. But situations where people are scrambling for definition far too close to the end of the sprint happen all too often, and, for instance, an excessively scaled-back interpretation of what constitutes an MVP can be forced on a group by time and pressure. And post-ship, more cycles of examination, meeting, and revision need to occur.

When “Agile” become “Ad hoc” it’s no longer the methodology in play, even if people keep saying the right words. Design as a system is a great example. A UX team needs to hypothesise a little more, ahead of time, so that iterative cycles appeal to an existing set of (flexible) design decisions rather than being built for the first time again and again. Of course, perfection isn’t the goal in any given release; it’s asymptotic by nature. But there’s a lot at stake, even when shipping seemingly small things. Users have plenty of competitive options.

The agile stereotype is seductive in its ease and apparent clarity to fall back into like a comfortable chair. It's a relaxing idea. Less is more. Things work themselves out if we collaborate and iterate. It's the swirling intensity of the tech life. We do what it takes to get it done, right? It’s all about code! Agile is meant to be less linear and hierarchical, and more circulatory and cooperative. And that’s a wonderful thing as long as perception doesn’t get to a point where anything that seems at all prescriptive is suspect. Agile, used as a buzzword, is one that people speak when it’s convenient (I don’t have time to spec this feature) and ignore when it’s not (The devs already built this feature and don’t want to change it now). Rapidly ideate and test… fail fast. What does fast mean? If a little up-front work can minimise the risk of failure and reduce walk-backs, why accelerate towards doom at a greater rate than necessary?

Removing sequence or linearity to ways of working results in incompletely thought-out product ideas and imprecise design. Even in a healthily firing agile team, there’s a place for an initial declamation of an idea, an estimation of its concrete value, a description of the planned interactions between system and user. These hypotheses, when recorded and defined initially, let designers attack a problem in the language of interaction and layout with much more lucidity. A clear set of design artefacts lets developers speed up their coding and understand the function and value of what they’re building.

“- I think we need to add some annotations to the wires so the devs have a better sense of how this will work…

- We’re being agile, so let’s just cover it live in stand-up.”

Agile isn’t meant to eliminate documentation – it just reduces it to the requisite information to inform designers and developers about what to do. What happens if nobody records any ideas? How well can we expect to remember the justifications that made sense a month or two or three ago? As products gain complexity, how can we expect to go back and revise ideas that don't exist accountably anywhere?

It’s a balancing act – a team can’t slog through reams of minutiae, but if all the intent, functional detail, and interactions are only conveyed verbally, the likelihood of successful implementation begins to degrade immediately with the inevitable dissolution of memory. A quick check of an abstract, a use case, a wireframe, a style guide, will save much more time and effort than reconvening a group to go over the facts of the case repeatedly.


Why it’s useful to think and write rather than only think.

It’s a very common issue that product teams and PMs don’t take the time to write formal or informal use cases prior to launching into the UX and build phases of a project. Cursory user stories, a title field in Jira, or even verbal delivery of intent are often meant to suffice. The diligence of writing down specs, tactical details of how something is supposed to work, interactions between user and system, is a way of making the nebulous concrete, a mechanism for interrogating one’s own assumptions, biases and ideas. When designers are wireframing on the basis only of one or two group conversations, trouble lies ahead. When developers are coding based on wireframes that are based on group conversations, we’re going to be revisiting the feature prior to launch, dollars to donuts. Writing things down helps a group respond to change, because the reason for a feature and its intended functionality is right there, clear as day, ready to be revised or overturned.

Lofty concepts and whiteboard sketches simply are not enough. The act of writing is a crucible for ideas, a gate to pass. If ideas aren’t diligently articulated to a sufficient level of detail, designers and developers can end up trying to create tangible interfaces from fuzzy, consensus-driven thought. Apocryphally at least, Bezos used to require that PMs express product concepts in a simple paragraph of text… not in deck form. Boiling ideas down to their essence is the first test of their intrinsic value. If it can’t be communicated in concise, plain language, then there’s a problem. This prevents hand-waviness, prevents the natural charisma of a speaker from influencing the room more than the idea itself. Writing closes the gaps that are often filled by charm, confidence, groupthink, hope, and even desperation.

The due diligence of product ideation and management is critical to narrowing the gap between what’s envisioned and what actually gets built. It might sound a little like waterfall to have some ordering to these events, but it’s really just some up-front time investment that makes more development happen faster as products inevitably grow and morph. There will be plenty of opportunity for collaboration; silos need not form. Change will always happen and how a team reacts to it is a test of their dedication to the agile methodology. Write down just enough to avoid human foibles. It’s motivating for engineers to know why they’re building what they’re building; it’s motivating for the group, an extra alchemical element, to rally around a collected understanding of the product.

In a platform environment where different services, all moving quickly, have to understand their relationship to each other, clarity will pay back much more than the time it took to harden the ideas with requisite documentation. Agile, performed by rigorous PMs at the outset, is a satisfying way of working that generally leads to better products in more users’ hands, added business value, and happier, motivated teams.

Five tips for strong PMing and solid documentation:

1. Remain customer-obsessed at all times. This doesn’t mean you can forget about the business, but rather that you focus on the customer’s goals in the context of typical tasks and mindsets, then work with the PPM to connect and effect the goals of the business.

2. Always be specting, questioning and challenging Start with a template for writing use cases. Alistair Cockburn’s approach is tried and tested. Remember that one need write only as much as will achieve a collective understanding and general assent among the business, Product, UX, and Engineering on intent, function, and direction.

3. Organise the product documentation along Agile principles: Theme, initiative, epic, user story/use case. This helps the PM prove what higher-level company themes are being met by more granular everyday work.

4. Collaborate/Elaborate. Share the spec documentation with all stakeholders for vetting and group clarity. A use case, a design element, a piece of code, and a consumer’s experiential moment are all the same thing viewed through different sides of a prism. If it doesn’t make sense to someone in the working group, there might be an issue to address before it’s out in the wild.

5. Get comfortable (and try to make those around you comfortable) with indeterminacy. At some level Product and UX are about committing to unknowns, and oracles are hard to find. Have a map to guide direction, data to support hypotheses, and break down intent and initiatives into measurable, tactical, executable pieces. A PM with their head-in-the-clouds will run into trouble, so stay focused on consumer reactions and KPIs. The fun (and responsibility!) really begins post-shipping.

Graeme Fordyce

VP Product/UX

Drawing on experience in diverse fields including search, payments, e-commerce and SEM, Graeme has been hands-on with all things product related since the late 1990s. He works with our clients to simplify the complex and drive effective product thinking with an emphasis on tactical execution and consumer empathy. Before joining Endava, Graeme spent time working with both high-tech start-ups and world-renowned brands. When he isn’t thinking about all the ways to improve products, Graeme enjoys chess, rugby, and landscape photography.


From This Author

  • 10 April 2020

    The Four Pillars of Truly Digitised Organisations – Part 2

  • 03 April 2020

    The Four Pillars of Truly Digitised Organisations – Part 1



  • 06 December 2023

    It’s In the Details: How Personalisation is Driving Digital Retail

  • 05 December 2023

    When Considering Synthetic Data, Answer These 3 Questions

  • 28 November 2023

    Moving Towards Global AI Regulation, an Update

  • 24 November 2023

    Marketplace Models and the Future of Airline Retailing

  • 21 November 2023

    Unlearn Churn: How Predictive Analytics Can Improve Retail Customer Retention

  • 16 November 2023

    Hi, I’m Matt Cloke

  • 15 November 2023

    How Microbetting Is Creating a More Engaging Fan Experience

  • 09 November 2023

    Learning the ecosystem lessons

  • 03 November 2023

    10 Groundbreaking Edtech Trends Revolutionizing the Future of Education

  • 02 November 2023

    What’s Shaping the Future of Capital Markets? 6 Takeaways from OPTIC

  • 31 October 2023

    Using Tech to Maximize the Impact of Major Sporting Events

  • 30 October 2023

    How to Streamline Your Retail Operations Through Selective Stocking

  • 19 October 2023

    Why Retail Margins are Tightening (and How to Protect Yours)

  • 13 October 2023

    Why Ground Operations Need Digital Transformation to Cope with Demand

  • 11 October 2023

    MWC Las Vegas: 8 Key Takeaways in Telecommunications

  • 09 October 2023

    Going Green: 5 Ways to Enjoy Leisure Activities Responsibly

  • 06 October 2023

    How Airlines Can Win a New Generation of Passengers

  • 26 September 2023

    Who Wins Most from Healthcare’s AI Transformation?

  • 21 September 2023

    Why Loyalty Programs Matter More Than Ever in Retail

  • 20 September 2023

    What Businesses Need to Start Innovating

  • 14 September 2023

    The Spark That Drives Machine Learning to Shine

  • 08 September 2023

    Why Customer Experience is at the Heart of Supply Chain Management

  • 07 September 2023

    How Offer and Order Management Systems Are Expanding The Aviation Business Model

  • 25 August 2023

    Tuning Out the Noise: Picking the AI for Practical Business Impact

  • 24 August 2023

    Resetting the Status Quo – How Banks Can Overcome Payments Challenges

  • 17 August 2023

    Opening Lap: An Endava and Toyota Racing Development Q&A

  • 17 August 2023

    The AI Boost in Gaming: Gameplay, Narrative and Production

  • 08 August 2023

    How Healthtech Simplifies and Secures Payments Processing

  • 14 July 2023

    Streamlining Digital Media Supply Chains with Generative AI

  • 13 July 2023

    4 Areas for Financial Institutions to Consider When Starting Out with Real-Time Payments

  • 12 July 2023

    Regtech - Necessary evil or competitive edge?

  • 07 July 2023

    Prime and Thrive: 3 Steps to Build Your International Payments Model

  • 06 July 2023

    Real-time Fraud – Solving the Virtual Pocket-Picking Problem

  • 29 June 2023

    Salut! I’m Radu Orghidan

  • 14 June 2023

    Debunking the Myths on Generative AI: What Is the Reality Behind the Most Common AI Misconceptions?

  • 31 May 2023

    The Time Is Now to Start Thinking About Real-Time Payments

  • 25 May 2023

    An Anatomy of the Data-Driven Retail Supply Chain

  • 23 May 2023

    BNPL regulation to protect consumers and control third-party lenders

  • 16 May 2023

    Salut! I'm Adriana Calomfirescu

  • 15 May 2023

    Hi, I'm David Boast

  • 12 May 2023

    The Business Impact of Fan Engagement: How to Leverage Technology to Improve Loyalty

  • 09 May 2023

    Staying Relevant - Why Merchants should embrace alternative Payments methods

  • 02 May 2023

    How IoT is changing Insurance

  • 26 April 2023

    A Veteran Game Developer's Perspective on Tool Development

  • 24 April 2023

    How Digital Ecosystems Enhance the Healthcare Experience

  • 21 April 2023

    Green Machines How Tech can Help Companies Hit Net-Zero Targets

  • 20 April 2023

    The Role of People and Technology in the Future of Underwriting

  • 19 April 2023

    Media 2030: Why Advertisers And Publishers Are Racing To Find New Strategies

  • 18 April 2023

    Alright, I’m Adrian Sutherland

  • 14 April 2023

    How Synthetic Data Could Solve Patient Privacy Dilemma

  • 11 April 2023

    Payments Makes The World Go Round

  • 06 April 2023

    Higher Fidelity Good Outcomes Harnessing FCAs Consumer Duty

  • 05 April 2023

    AI in Pharma: How Machine Learning is Transforming Drug Development

  • 04 April 2023

    Hello! I’m Leane Collins

  • 31 March 2023

    The Dos and Donts of Carve Outs Private Equity

  • 30 March 2023

    Cage Of Reason: Fca's New Consumer Duty Heralds The Rise Of The 'Reasonable Insurer'

  • 28 March 2023

    A Legal View on the Ownership and Future of AI-Generated Works

  • 24 March 2023

    Championing Women In Tech

  • 23 March 2023

    5 Ways Capital Markets Companies Can Ensure Resilient Operations

  • 15 March 2023

    Buenas! I’m Leticia Chajchir

  • 14 March 2023

    4 Ways To Improve Customers’ E-commerce Search Experience

  • 28 February 2023

    4 Healthcare Innovations that Can Benefit People and Profit

  • 21 February 2023

    Hey, I'm Lewis Brown

  • 17 February 2023

    Top Considerations for Financial Services Providers entering th Cross-Border Payments Space

  • 13 February 2023

    Better Together Harnessing The Power Of Digital Ecosystems

  • 09 February 2023

    What to Include in a Customer Re-Engagement Content Library

  • 07 February 2023

    Supercharging Wealth Management with Hyper-Personalisation

  • 02 February 2023

    How Innovating the Insurance Customer Journey creates a Competitive Advantage

  • 30 January 2023

    G'Day, I'm David Marsh

  • 26 January 2023

    Empowering Underwriting and Unlocking Revenue with Legacy Insurance Data Sets

  • 24 January 2023

    Four Stakeholders who win the most when Healthcare innovates

  • 23 January 2023

    Journey to the Centre of the Cloud with AWS - Part 3

  • 20 January 2023

    Journey to the Centre of the Cloud with AWS - Part 2

  • 18 January 2023

    Journey to the Centre of the Cloud with AWS - Part 1

  • 17 January 2023

    The 4 Most Common Mistakes in Retail Site Design

  • 13 January 2023

    Boost and bolster your innovation. Three tips to help get it to the next level

  • 10 January 2023

    5 Questions in Smart Energy that will define the Net Zero Transition

  • 19 December 2022

    Looking ahead and helping our customers do the same

  • 16 December 2022

    Stepping forward - The State of Cross-Border Payments in Southeast Asia

  • 14 December 2022

    Tech and Tinsel - Another Holiday Q&A with some of our Execs

  • 13 December 2022

    Why should Payment Service Providers be thinking about adding an ISV?

  • 07 December 2022

    How AI and Automation are revolutionising microscopy

  • 07 December 2022

    Venturing into the Metaverse to build an Innovative Bridge to Our People

  • 05 December 2022

    An Australian Eye on the Global Effort to Improve Cross-Border Payments

  • 29 November 2022

    How Reverse Logistics are Turning E-commerce Green

  • 23 November 2022

    5 things we learned at World Aviation Festival 2022

  • 23 November 2022

    Cyber Security Incidents in Australia Highlight the Need for a Balance Between Risk and Innovation

  • 22 November 2022

    The Era of Ecosystems and the Rise of Open Insurance

  • 18 November 2022

    How Tech is changing Sports betting for the better

  • 16 November 2022

    4 Ways Insurers Can Leverage Technology to Differentiate Themselves

  • 16 November 2022

    The Future of Banking in the Nordics - Being Digital and Personal

  • 15 November 2022

    Staying Relevant in the Buoyant Cross-Border Payments Market

  • 15 November 2022

    3 Experts' Insights on the Complicated Relationship between Fintechs and Banks

  • 09 November 2022

    How can banks create a secure, optimised cloud-enabled architecture?

  • 08 November 2022

    Tech is Good for you: How Wearable Edge Devices Changed Healthcare

  • 01 November 2022

    How Microservices can upgrade the Customer Experience

  • 25 October 2022

    How Technology can help Monitor the Circular Economy

  • 18 October 2022

    Why it's Time for Banks to let go of Legacy IT

  • 11 October 2022

    Buy vs. Build in Banking: Which Option is Right for You?

  • 04 October 2022

    The Rise of Super Apps: How Banks can compete

  • 28 September 2022

    AI Art in Game Production – an XDS 2022 Table Discussion

  • 20 September 2022

    Payments Data Monetisation is Key to Driving Sustainable Growth

  • 13 September 2022

    Navigating the Healthcare Ecosystem

  • 30 August 2022

    hey y’all! I’m Ashley Grant

  • 23 August 2022

    5 Ways to Fix Your Data Spine in Banking

  • 16 August 2022

    De-risking Digitalisation

  • 09 August 2022

    hi, I’m Brian Estep

  • 02 August 2022

    hey! I’m Lia Rollman

  • 19 July 2022

    The New Ways of Issuing Cards

  • 12 July 2022

    Scores on the Door: Rating Autonomous Vehicles

  • 06 July 2022

    We’re in Nottingham – a Q&A on Endava’s New Delivery Centre in the UK

  • 06 July 2022

    Data-Driven Impact: Don’t Settle for Less

  • 06 July 2022

    hey, I’m Chris Hart

  • 28 June 2022

    Platforms: a Blessing or a Curse?

  • 23 June 2022

    A Payments View on Marketplaces – How to Be(come) Successful

  • 21 June 2022

    Intelligent Commercial Underwriting

  • 14 June 2022

    The Future of Supply Chain: What’s Next?

  • 31 May 2022

    The Future of Autonomous Vehicles in T&L

  • 27 May 2022

    Hello! I'm Hannah McCarthy

  • 24 May 2022

    Going Native: Why Cloud-Native Services are Essential

  • 19 May 2022

    How to Tackle Legacy – Breaking Down Walls Between Change and Run

  • 17 May 2022

    Advantages of a Yard Management System

  • 13 May 2022

    Are Phones About to Become the New POS Terminals?

  • 10 May 2022

    The Digital Economy is an Upgrade of Smart Cities and Communities

  • 05 May 2022

    hello! I’m Sumita Davé

  • 03 May 2022

    Physical Automation in the T&L Industry

  • 28 April 2022

    zdravo! I’m Andrej Kotar

  • 26 April 2022

    Open Banking in the US

  • 20 April 2022

    hello! I’m Paul Maguire

  • 19 April 2022

    Digital Automation in the T&L Industry

  • 12 April 2022

    How Do Banks Embrace Embedded Finance – Have the Fintechs Already Won?

  • 06 April 2022

    ESG Data Architecture is a Business Imperative – How to Get Started

  • 05 April 2022

    hi! I am Roy Murphy

  • 05 April 2022

    Modernizing the Shipping and Cargo Process

  • 30 March 2022

    The Metaverse Evolution and Learning from the Games Industry

  • 30 March 2022

    Do Androids Dream of Trading Electric Sheep for Digital Wood? An Introduction to Automated Game Design

  • 23 March 2022

    Real-Time Payments in Australia – Why Corporates Should Get on Board

  • 22 March 2022

    Current Challenges in the Transportation & Logistics Industry

  • 16 March 2022

    bok! I’m Sanja Cvetkovic

  • 15 March 2022

    Rapidly Transforming: Healthtech Trends in 2022

  • 08 March 2022

    How to Digitize Warehouses and Distribution Centers

  • 01 March 2022

    Top Challenges in Warehouse and Distribution Centers

  • 28 February 2022

    Tackling CIB Legacy at its Core

  • 23 February 2022

    salut! I am Isabela Buhai

  • 22 February 2022

    4 Buy Now Pay Later Trends Set to Disrupt the Industry

  • 15 February 2022

    salut! I’m Natalia Ciobanu

  • 14 February 2022

    Product-Led Innovation – a Q&A with Joe Dunleavy

  • 02 February 2022

    Buy Now Pay Later: Will Regulation Burst the Bubble?

  • 31 January 2022

    Innovation Will Spur Ireland’s Race to the Top

  • 28 January 2022

    The Value of Digital and Automation in the Product Returns Process

  • 26 January 2022

    Virtually Disrupted? Keeping Pace with Accelerating Customer Expectations

  • 19 January 2022

    The 3 Big Ps in Modern Insurance: Personalisation, Prediction and Prevention

  • 19 January 2022

    An Introduction to Mobility as a Service in the US

  • 12 January 2022

    hello! I’m Paul Willoughby

  • 12 January 2022

    Buy or Build? A Game-Changing Question in Insurance

  • 11 January 2022

    Payment Service Providers 2.0

  • 21 December 2021

    Making a Positive Impact Through Giving

  • 14 December 2021

    From Global Pandemic to Holiday Spirit – a Q&A With Some of Our Senior Execs

  • 07 December 2021

    Hand in Hand with Artificial Intelligence in the Energy Sector

  • 03 December 2021

    Evolving Digital Self-Service in Insurance

  • 29 November 2021

    zdravo! I’m Ilija Gospodinov

  • 24 November 2021

    yes folks, I’m Joe Dunleavy

  • 09 November 2021

    hi there! I’m Tony Whitehorn

  • 03 November 2021

    Operating Responsibly for Future Success

  • 02 November 2021

    Leveraging ESG Data to Grow Your Business

  • 26 October 2021

    Smart Tech: Providing the Visibility Supply Chains Need

  • 12 October 2021

    hello! I’m Scott Harkey

  • 05 October 2021

    How to Improve Intelligent Energy Storage Systems Using AI

  • 28 September 2021

    Data-Driven Insurance

  • 21 September 2021

    hi y’all! I’m Antony Francis

  • 14 September 2021

    Once Upon a Time … in Payments

  • 31 August 2021

    Personalised Banking: How to Get Ahead of Ever-Changing Client Value Propositions

  • 17 August 2021

    RPA: Using Robots to Streamline Processes

  • 10 August 2021

    The Inclusive Workplace of the Future – a Q&A with Asif Sadiq MBE

  • 03 August 2021

    hello! I’m Elisabeth Bradley

  • 27 July 2021

    How the Board Game Catan Conquered the Digital World

  • 13 July 2021

    The Transformation Trifecta: Cloud, Digital and Open Banking

  • 06 July 2021

    How to Future-Proof the Digital Retail Experience

  • 23 June 2021

    hi! I’m Thomas Bedenk

  • 17 June 2021

    Hello! I’m Adrian Bugaian

  • 18 May 2021

    4 Techniques to Fix Digital Breakages in the Supply Chain – Part 2

  • 11 May 2021

    Phygital in Automotive: Bridging the Gap Between Physical and Digital – Part 2

  • 05 May 2021

    Artificial Intelligence: Where Does The Real Value Lie?

  • 27 April 2021

    4 Techniques to Fix Digital Breakages in the Supply Chain – Part 1

  • 20 April 2021

    Phygital in Automotive: Bridging the Gap Between Physical and Digital – Part 1

  • 14 April 2021

    What ‘We Care’ Means at Endava – a Q&A on Sustainability with our CEO

  • 08 April 2021

    Before Commission / After Digitisation – a Pivotal Era for Australian Payments

  • 06 April 2021

    Insurance Insights: Low Code

  • 30 March 2021

    Insurance Insights: Intelligent Underwriting Workbench

  • 23 March 2021

    The Challenge of Technology is Not Technology

  • 18 March 2021

    Supporting and Empowering Women in Tech

  • 16 March 2021

    Insurance Insights: Customer Retention & Cross-Selling

  • 09 March 2021

    Insurance Insights: Cloud Migration

  • 02 March 2021

    How to Improve Interoperability in Healthcare

  • 23 February 2021

    Insurance Insights: Data Exploitation

  • 16 February 2021

    Insurance Insights: Open Insurance

  • 11 February 2021

    Mapping the Future Applications of Artificial Intelligence

  • 18 December 2020

    Celebrating 20 Years of Endava – with Julian Bull

  • 15 December 2020

    Insurance Industry Trends from DIA Prime Time

  • 08 December 2020

    Celebrating 20 Years of Endava – with Rob Machin