8 Product and domain modernization

 

This chapter covers

  • Modernizing the UX, product, and domain
  • Determining better requirements for modernized applications
  • Staffing teams with design and discovery expertise
  • Designing future states with process modeling EventStorming and Domain Storytelling
  • Establishing a common language

A comprehensive approach is required to exploit the full potential of modernization. Modernization is often perceived as technological change, but the benefits extend far beyond that. It’s also an opportunity to revamp the user experience, improve the value provided by your products, address those frustrating problems that have existed for years, and remove unneeded complexity.

It’s common to see employees left with barely usable solutions involving green screen mainframes or 1990s-style UIs, often part of complex manual processes. These types of inefficiencies can grow into huge problems as organizations scale or as more complexity is bolted on top. Understanding what users really need will also highlight what is no longer required and can be deleted rather than modernized, saving valuable time and costs.

8.1 Industry example: Business property tax modernization

8.2 Identifying product requirements

8.2.1 Involve the right people

8.2.2 Identify the costs of not modernizing

8.2.3 Don’t mindlessly reverse-engineer the code

8.2.4 Analyze system information

8.2.5 Spend time with real users

8.2.6 Continuous discovery

8.2.7 What have people given up asking for?

8.2.8 We’ve always done it that way

8.2.9 Finding shadow IT