RAD Doesn’t Mean Ugly Architecture

Professional Services Directors at OutSystems

Nuno Teles Miguel Baltazar

Utilities

Banking Retail

HealthCare

Challenges for an Enterprise1. Disbelief in Big Bang Projects

delivery from 4 to 20 weeks

2. Reinvent customer engagement is neededmobile is changing the way companies do business

3. Optimize backend operationsbeing able to change your processes in 6 to 24 weeks

4. Support business innovationwith digital innovation

Digitization is a must!Most important measures used to assess effects of digital efforts, % of respondents¹

¹ The online survey was in the field from April 21 to May 1, 2015, and garnered responses from 987 C-level executives representing the full range of regions, industries and company sizes; 13,5% of these executives have a technology focus. Multiple responses were allowed.

Source: See the McKinsey survey on digitization, “Cracking the digital code: McKinsey Global Survey results”, September 2015, mckinsey.com

36

36

32

36

28

21

23

28

9

Impact on profits

Impact on customers behavior (ie, purchases, loyalty)

Impact on customer satisfaction (ie, decrease in resources required)

Impact on current top-line sales

Impact on future top-line salesImpact on brand awarenessReturn on digital investment

Other

Impact on organization efficiency (ie, decrease in resources required)

I want to innovate my business but...How do I migrate from a legacy system to a new digital platform?

How can I move from an existing process to a digitized one and well performed?

How can I achieve those without loosing, scalability, performance, enterprise-grade best practices?

Where do I start?

Stepwise approach

• Identify your As Is, Blueprint your To Be

• Establish your Journey

• Identify your First App

Moving from As Is to the To Be

Customer ExampleAs Is

Customer ExampleTo Be

Backends

Legacy CRM

Master Data

Order Entry Access DB BackOffice App

Customer

Customer ProvisioningAs Is

Legacy Order Mng

Backoffice

Order Tracking

ERP

Working in two speeds

Backends

Customer Portal

Customer ProvisioningTo Be

ERP

Order Mng Account Mng CRM

Web Mobile Notifications

Operations Portal

Middleware

micro services micro services micro services

Customer Backoffice

How do you get there?Your First App

First Application Characteristics

• Small to mediumso that it brings value quickly

• a major pain, visible to your leadershiplots of users/customers that really need it

• Mobile enabledto showcase innovation

• 2 Critical Integrationsfoundation for the integration model that does NOT stall the project

Backends

Legacy CRM

Master Data

Order Entry Access DB BackOffice App

Customer ProvisioningAs Is

Legacy Order Mng

Order Tracking

ERP

Customer Backoffice

Backends

Legacy CRM

Master Data

Order Entry Access DB BackOffice App

Customer Provisioningnew CRM

Legacy Order Mng

Order Tracking

ERP

Customer Backoffice

Backends

Legacy CRM

Master Data

Order Entry Access DB BackOffice App

Customer Provisioningnew CRM

Legacy Order Mng

Order Tracking

ERP

Operations Portal

CRMmicro services

Customer Backoffice

Backends

Customer Provisioningnew CRMng

Order Tracking Operations Portal

Master Data

Legacy Order Mng

ERP

CRMmicro services

Customer Backoffice

Order Entry

What about the next ones ?

Second Application Characteristics • Reusable micro services

gradually carve out and create your services

• Focus on business valueyour priorities should maximize the highest business value upfront

• User reachcovering multiple channels and departments compound benefits

• Keep your Apps freshYour existing apps also need attention, value V2 of existing apps against your new apps

Backends

ERP

Customer Provisioningnew CRM

Order Tracking Operations Portal

Master Data

Legacy Order Mng

Customer Backoffice

Order Entry

CRMmicro services

Backends

ERP

Customer Provisioningnew CRM

Order Tracking Operations Portal

Master Data

Legacy Order Mng CRMmicro services

Order Mng

Customer Backoffice

Order Entry

micro services

Customer Portal

micro servicesmicro services

Backends

Customer Provisioningnew CRM

Operations Portal

Master Data ERPCRM

micro servicesOrder Mngmicro services

Customer Backoffice

Customer Portal

Backends

Customer Portal

Customer ProvisioningTo Be

ERP

Order Mng Account Mng CRM

Web Mobile Notifications

Operations Portal

micro services micro services micro services

Middleware

Customer Backoffice

Architecture Best PracticesGuidelines and Common Pitfalls

Common Pitfalls?Unable to cope with Change

Enterprise Architecture must embrace innovation, providing the core's out of the box, and support for innovation

Lack of Practical GuidanceEnterprise Architecture is there to make teams efficient not to mandate a

model per se. It’s the group responsibility to enforce the Architectural guidelines to the teams

Weak Governance Lacking an empowered Architecture Leader/Team

GuidelinesBe Pragmatic

built for what you know and a bit ahead, be prepared to add components along the way

Blueprint where you want to goLooking at the As Is alone can lead to a “ugly” To Be, know where you’re going

Architecture as a movie instead of a snapshotset up a continuously evolving process, this is just the start of a continuous

business alignment

Thank You!Q&A