Design Process

Our Story

Who We Are
The Pega Design team is the official Pegasystems design organization committed to product excellence.

What We Do
We take responsibility for the design of each product by dividing our work into three domains: development and app-configuring experiences, employee application experiences, and end-customer experiences.

Why It Matters
We believe everything Pega produces should be best-of-class in usability and should be executed exactly according to the design.

Why It’s Better
As owners of the experiences of Pega products, Pega designers work cross-functionally to deliver the only design resources that enable you to build for change.

Last updated: Jul 2019

Our Projects

Pega Design’s primary focus is the product usage and the end users of our products. Because our work must align with strategic and execution initiatives and general product initiatives, we split out work into three categories: corporate growth, innovation, and maintenance.

  • Corporate growth (60%): Design work for products/features that have current pipeline.

  • Innovation (30%): Design work for products/features that we believe will have pipeline in a year or two years.

  • Maintenance (10%): Non-growth product with design debt.

As a small team, we work efficiently, evolving innovative Design Ops techniques, and making decisions on where our work will add the greatest value. Our design process — that is iterative, collaborative, and transparent — enables us to do simply that.

Last updated: Jul 2019

Our Collaboration

Strong outcomes requires strong collaboration. Strong collaboration requires strong communication. In order to work effectively, Pega Design enters into every project with three key stakeholders — the designer, product owner, and engineer. As a result of this trio, Pega takes advantage of the diversity of expertise for the purpose of co-creation.

Last updated: Jul 2019

Our Way of Working

Business Value Stage

To first start achieving the highest value, we discover and document the business goals of a product or feature. These should be described as business issues that need to be solved and should not presume any solution. Designers know we are ready to move to the next stage when we have a document detailing business goals, approved by the highest relevant stakeholder.

Participants:
  • Designer
  • Product Owner
  • Subject Matter Expert
  • Stakeholders
  • End-Users
  • Product Marketing

Research Stage

Research is about building an understanding of our end users as well as understanding the feasibility and size of the design work. The designers, product owner, and engineering owner work together to align user needs that also solve business issues. Furthermore, designers are expected to make internal documents or assets of requirements, such as user flows, interview transcripts, competitive analysis, or initial information architecture.

Participants:
  • Designer
  • Product Owner
  • Engineering Owner

Concept Design Stage

Using tools such as whiteboards, low-fidelity wireframes, and paper prototypes, Pega Design builds a validated vision of a potential solution. Our role in this stage is to determine if we as Pega have the current paradigms that work for these use-cases or determine if there is an alternative design. Moving through phases of diverging and converging on work, we collaborate and critique with the rest of the Pega Design Team, stakeholders, and end-users through usability testing. The expected result of the Concept Design Stage is then the creation of internal design documents with the validated vision that is vetted by research and approved by the UX Owner and a relevant platform/strategic application UX Lead.

Participants:
  • Designer
  • Product Owner
  • Engineering Owner

Documentation Design Stage

Design work begins to be more solidified when moving into the Documentation Design Stage. The Engineering Owner works with the Product Owner to determine what needs to be done for an Epic, in Agile Methodology, to be considered ready to begin development. At Pega, we call this document an Epic Definition of Ready (EDOR). Using previous stage results and hi-resolution validated designs, the team delivers the approved design POCs with the EDOR. These designs include Sketch prototypes and any other project-dependent assets.

Participants:
  • Designer
  • Product Owner
  • Engineering Owner

Build Stage

After high-fidelity prototypes have been handed over, designers stay involved in development by monitoring progress and assisting the Product Owner and engineering team during implementation. If new feasibility issues arise, designs are modified accordingly. The final outcome is a “pixel-perfect” implementation of the design. During this time, designers also stay engaged by relaying achieved business value of design work to Pega Marketing and engaging with documentation and enablement.

Participants:
  • Designer
  • Product Owner
  • Engineering Owner
  • Team
  • Marketing
  • Documentation

Release Stage

The release stage is about finishing a project with as much strategic vision as the beginning phases had. The design team conducts a retrospective wrap-up of the product or feature shipped and create a plan for improvements to be enacted during the next Sprint or release. All involved stakeholders monitor post-release usability and value to the market. It is possible designers will begin to create a case study of the project to be shared at the internal Product Design Monthly meeting or to be shared on our blog platform.

Participants:
  • Designer
  • Product Owner
  • Engineering Owner
  • Marketing

Last updated: Jul 2019