openSAP

SAP Leonardo Design-Led Engagements

Demystified
Section 1 Unit 3

00:00:08 Hello, and welcome to Leonardo Design-Led Engagements Demystified. I'm Hailey Temple, a
member of the SAP Design Team responsible for enabling success
00:00:18 in Leonardo design-led engagements. I'm one of your instructors in this course, and together,
we will walk through the end-to-end Leonardo design engagement process.
00:00:28 When you complete this course, you will understand the goals, activities, deliverables, and
people involved along each step of the Leonardo design-led process.
00:00:38 You will be able to articulate the value of the process with peers and customers, plus start your
journey to becoming part of a Leonardo project.
00:00:46 So, let's get started.
Section 1 Unit 4

00:00:05 Let's start with a short overview of Leonardo, and why we are using Design Thinking as part of
these engagements.
00:00:11 SAP Leonardo is our digital innovation system. We combine new technologies, focused around
leveraging data to simplify business processes,
00:00:22 with Design Thinking as part of our Design Services offerings, which is an approach that puts
the end user at the center of solving this business problem.
00:00:33 The SAP Leonardo tagline is: intelligently connecting people, things, and businesses. But let's
dig in a little deeper here.
00:00:43 Executives feel increasing pressure to innovate and to create a digital business, one that
delivers real-time insights, can predict their customers' needs, and adapt quickly.
00:00:55 The technology is available, but it's hard to know which technology to adapt to solve these
challenges. Plus, which problem is the most valuable to solve?
00:01:05 With SAP Leonardo, we offer an approach where we work together with the customer to co-
innovate, bringing our technology expertise and a design-led approach to tackle their biggest
business challenges.
00:01:18 This honeycomb structure represents the technology capabilities of SAP Leonardo. At the top,
you see Design Thinking as the key process
00:01:27 that drives SAP Leonardo projects forward. We won't cover these technology capabilities in
detail as part of this course,
00:01:35 but rather focus on the value of Design Thinking throughout this process. It's necessary to use
Design Thinking with SAP Leonardo projects
00:01:44 because it's how we co-innovate with our customers quickly and keep the team focused on
solving a problem that goes beyond just the business,
00:01:51 but one that improves the human experience for people affected by this business problem.
Design Thinking helps us drive innovation by thinking about three key factors:
00:02:02 feasibility (the technology factors), viability (the business factors), and desirability (the human
factors).
00:02:12 When we consider these factors and work to balance them together, we identify and create
opportunities to innovate and solve a problem that satisfies these needs.

2
Section 2 Unit 2

00:00:03 Let's begin by talking about the SAP Leonardo design-led engagement core components. First,
the fact that we're using a proven design-led innovation process
00:00:14 based on over ten years of experience driving design projects. Second, we use design tools like
SAP Build to create prototypes
00:00:24 and collect user feedback through design studies. Third, we use the SAP Fiori design language
to create simple, responsive, and delightful user experiences
00:00:33 when we create a solution. And finally, we work with design experts to make sure our use case
and the user interface help solve a business challenge
00:00:42 through what we call Design Gates. We'll dive into these four core components throughout this
course.
00:00:49 The Leonardo design-led development process is made up of four phases: Explore, Discover,
Design and Prototype, and Deliver.
00:01:01 There are also key checkpoints along the way between phases, called Design Gates or D-
Gates.
00:01:06 These elements make up a comprehensive design process for Leonardo engagements. And
we'll dive into the details of each phase and Design Gates in later modules.
00:01:18 Before we move forward, it's important to talk about the two potential tracks for your Leonardo
customer engagement.
00:01:26 Every customer engagement goes through the Explore phase to identify the use case that we
want to investigate more in the Leonardo process.
00:01:35 Once we identify the use case, the project can go in two potential tracks: express or open
innovation.
00:01:44 The key difference between these two tracks are the timelines to deliver the proof of concept
and how much detail is involved in the process.
00:01:53 Open innovation, as it sounds, is a little bit more in-depth, where you do some deep user
research and maybe build the prototype
00:02:04 from scratch versus using something pre-made. The express engagement really ties in these
accelerators
00:02:11 that I'm going to talk a little bit more about next. For the express engagement, I mentioned these
industry innovation accelerators.
00:02:20 The accelerators are fixed price bundles of expertise, software, and design services that are
used to deliver proof of concepts much faster than open innovation engagements.
00:02:33 What's great about these is we already have an example prototype set up, we also have some
example personas we can use to validate with the customer and the end user,
00:02:43 so we're able to go through this design process and deliver a proof of concept much faster than
we would otherwise. Now if you don't have a use case that fits into an accelerator, it will become
an open innovation project.
00:02:57 But the idea is that these open innovation projects will feed into the accelerator portfolio so we
have a more expansive offering to our customers.
00:03:07 Before we dig into the details of these phases in our next module, let's make sure we check our
understanding with a quick quiz.

3
Section 2 Unit 4

00:00:11 Now it's time to talk about you. Where might you fit into one of these Leonardo engagements?
00:00:17 First, we have the customer design engagement lead, or CDEL. In this role, you manage a
Leonardo engagement from start to finish.
00:00:26 This means managing relationships, expectations, and deliverables with the customer and SAP
teams. You'll also facilitate conversations with participants during workshops.
00:00:38 Once you have more experience as a CDEL you will mentor new CDELs who are learning about
the role and responsibilities.
00:00:47 With these key activities in mind, it's necessary that a CDEL has experience as a senior Design-
Thinking coach, has extensive project experience,
00:00:56 and has some customer-facing experience. We know that some of these tools, like Build, Fiori,
or the design process,
00:01:05 may be new to some CDELs, so through trainings, you can increase your knowledge and
understanding of these new design tools.
00:01:14 So you can see the CDEL needs plenty of skills to get started, but they're definitely not working
alone. The CDEL depends on others from the SAP team to bring their knowledge and
understanding,
00:01:27 such as Leonardo experts, UX designers, and Build experts, to share their perspectives on how
to drive the engagement forward.
00:01:37 These SAP teammates also work with customer leads, like the sponsor, the business lead, and
end users, to make a successful engagement.
00:01:46 Leonardo design engagements are truly intended to be a co-innovation experience. Let's talk
more about the design expert's role and necessary skills.
00:01:57 The design expert is a customer design engagement lead's close ally in driving a successful
Leonardo design-led engagement.
00:02:05 They bring experience and kowledge, translating key insights from user research into the project
to make the solution feasible, viable, and desirable.
00:02:15 The design expert also creates the low-fidelity and high-fidelity prototypes in compliance with the
SAP Fiori design strategy.
00:02:24 Finally, they prepare artifacts from each phase for the Design-Gate review. With these
responsibilities in mind, a design expert needs skills and experience
00:02:33 doing design research, creating enterprise-grade user experience designs, and design testing.

4
Section 3 Unit 2

00:00:10 In the Explore phase, we're looking to prioritize the business scenarios and identify a use case
we want to drive forward in a Leonardo engagement.
00:00:19 We also want to define the design challenge, the key stakeholders, and a game plan that the
SAP and customer stakeholders
00:00:27 can use to drive a successful engagement. Let's learn more about the Explore phase from
Yvonne Waibel, a member of the SAP Design team.
00:00:37 Yvonne's going to go into detail about the Explore phase, more specifically, the Explore
workshop, where we talk with the customer about their key business challenges.
00:00:47 She really emphasizes the importance of the Explore phase and the workshop as part of this
design-led process.
00:00:55 Hi, my name is Yvonne Waibel, I'm part of SAP Design, and I'm here to talk to you about the
SAP Leonardo design process,
00:01:04 and from design to prototype. So what you see here on the slide, what we start with, is the
exploration workshop.
00:01:13 And the key differentiator of the exploration workshop, it's a Design-Thinking workshop, but it's a
Design-Thinking workshop that is actually focusing on the business.
00:01:21 So we're doing this exploration workshop with the business leaders and the business decision-
makers. So IT is actually not the main player here.
00:01:30 It's the business that we want to engage and who we engage with. And it's very exciting usually
for the business to come together
00:01:37 and get the opportunity to really share among each other, and with us, what their pains are, and
what their threats are, their barriers, and where their wishes are.
00:01:48 So an example, for instance, for the exploration workshop that we do is what you see here. So
after we've started an introduction of how we engage, what we do,
00:01:59 because it's a different way of working with SAP. It's not the SAP you know, it's the SAP you
need to know.
00:02:05 And here we're focusing really, after we have the process introduction and the Leonardo
introduction, we're really focusing on what are the business challenges.
00:02:14 What are the challenges that they're currently facing? What are the different issues you're
having?
00:02:19 And we group them, we cluster them in the groups, and then we're moving into what are your
wishes. Where would you like to go?
00:02:28 And from where you would like to go, the inspirational, the art of the possible that we have
earlier, usually gets them to open up, thinking out of the
00:02:39 thinking about are they really asking the right questions, because that's the whole purpose of
Design Thinking: Are we really fixing the right problem?
00:02:46 Are we asking the right question? So here we then actually go to the wish list.
00:02:51 We actually look at where they would like to go. What would they like to do with IoT? What
would they like to do with machine learning?
00:02:59 And things they haven't even thought about before. And that's where we then group this
together and help them prioritize.
00:03:06 So now looking at all the different issues you have, looking at all the threats that are coming up,

00:03:11 looking at all the wishes where you need to go, what is the value of fixing that? What are the
right use cases to do?
00:03:17 So at the end of the workshop we have a prioritized list of use cases. We have a stakeholder
map, because from the use cases, we go OK, who are the people participating in this process?

00:03:30 Who are the different end users as part of the process? Who are the people we need to talk to
as a next step to do the user research,
00:03:37 to really identify the users that are participating in this process? So it's a very valuable process
and it's a really valuable workshop

5
00:03:48 that gives us a lot of insight into their business, and creates a roadmap for them and creates a
roadmap for us
00:03:55 so that we continue putting them through the right path, especially with Leonardo. There are a
couple of different activities you're going through during the Explore phase,
00:04:07 so here's what you'll expect to come out with to drive your engagement forward. You'll be doing
alignment meetings and maybe some different calls with the customer sponsor
00:04:18 and the account executive, so you'll have lots of notes, and background, and preparation for
your engagement moving forward.
00:04:26 Working with the SAP and customer participants, you'll also identify the use case, or use cases
you want to drive forward with the Leonardo engagement,
00:04:36 noting that you will be thinking about whether it is an express or open innovation engagement.
You'll also be conducting a participatory workshop in the Explore phase,
00:04:46 and so you'll have some artifacts coming out of that workshop. We're not going to cover those
specific workshop activities in detail during this session,
00:04:56 but that is something you'll explore more in depth after the awareness training in a boot camp.

6
Section 4 Unit 2

00:00:10 Thanks for joining me for this next module, where we'll talk about the Discover phase. As we
mentioned in an earlier module, your team's activities in Discover
00:00:20 will depend on whether you are going on the express or open innovation track. Overall, the
Discover phase helps identify the current business process
00:00:32 to understand the needs of the end users and to define the "to-be" process that satisfies these
user, business, and technology needs.
00:00:41 The first round of prototyping also happens in the Discover phase using a low-fidelity prototype.
Let's continue to talk about the Discover phase with a quick explanation by Yvonne from SAP
Design Services.
00:00:58 Hi, my name is Yvonne, and I'm here to talk to you about the Discover phase. Usually, I get the
question "what is the Discover phase?"
00:01:05 And the Discover phase actually consists of two things: One is the user research, the on-site
user research.
00:01:12 As you see here, we actually go on site, to the actual end users, and we sit next to them, watch
what they do and observe.
00:01:22 Either one day or up to four days, it really depends on how many user groups we're going to
have, and we usually try to get three to four users per user group.
00:01:32 And so we sit next to them, either in the call center or maintenance workers, whoever we are
researching,
00:01:38 whatever we decided in the exploration workshop who the stakeholders are, those are the users
we want to observe in the end user research.
00:01:47 So that's the first step of the Discover phase. Then we're going to come back to our app house,
usually,
00:01:54 where we do our synthesis of all the user research that we found. So skilled user research and
designers, we're sitting here and we're creating an as-is process map,
00:02:05 so we basically annonymize what we found out, and what are the different patterns and where
are the different pain points, from what we observed of the users.
00:02:15 Like sometimes they put stuff on their notepad. We see that the questions are the same, there's
lots of opportunity for machine learning, there's stuff for predictive.
00:02:26 So all these things we see in the user research, and we create an as-is journey map. This as-is
journey map we then take into the next step of the Discover phase,
00:02:37 which is the participatory design workshop. In that workshop, we ask that from the customer the
end users, the business managers,
00:02:48 the process owners are participating in the design workshop with us. We're validating the as-is
process, we're doing "how might we" questions
00:03:00 and how might we alleviate the different pain points that we found and the areas of innovation,
and then we ideate and work with them to come up with a to-be process.
00:03:10 Then from that to-be process, we go and ideate again how can we solve and how can we
support with a solution this to-be process.
00:03:19 So by the end of the Discover workshop, the 2-day design workshop, we actually have a paper
prototype, ususally, for the different areas where we want to create a solution.
00:03:33 And for that, the people who are in the workshop really are very invested, because we're asking
for two days of their time, of their busy schedules,
00:03:43 to come in the workshop with us and work on the solution together. Could we do this on our
own? Absolutely. We could design it already based on the user research,
00:03:53 but the point is to have this participatory design workshop to make it their baby too. Because
then they invest time, they invest all their ideas,
00:04:02 and when they walk out of the workshop, I've only seen really happy business users, because
they can't wait to have the solution that they worked on with our guidance.
00:04:13 So from here, when we have the paper prototype, we put it in Build, and then the next step is
actually working on the actual design. Thank you.

7
00:04:25 OK, so a quick recap of Yvonne's explanation about the Discover phase. The Discover phase
contains two key parts: the user research and synthesis
00:04:36 and the participatory design workshop. Synthesis is an important step after the user research
00:04:43 because it helps the team identify what the as-is process looks like for the use case. The
participatory workshop is also important because it gives the customer sponsor
00:04:54 and the end users ownership over the process and what will be the proof of concept coming out
of the engagement. Here is an example of a defined as-is process created following user
research during the synthesis workshop.
00:05:07 You can see the different end users, actions, and thoughts involved in the process that give the
project a human-centric perspective.
00:05:15 You can see the contrast between the as-is and to-be processes. In the participatory workshop,
they take the as-is process,
00:05:24 validate it with the business stakeholders and the end users, and together, brainstorm what this
new process can look like.
00:05:33 Yvonne also mentioned paper prototyping in the Discover phase. This is an example of a low-
fidelity prototype
00:05:40 that the participants sketched during the workshop to imagine the to-be process and to-be user
interface.
00:05:47 This is the first version of the low-fidelity prototype the team can use to get user feedback and
further iterate throughout the engagement.

8
Section 5 Unit 2

00:00:11 Hello, and thanks for joining me for this next module, where we're going to talk about Design
gates and tools.
00:00:17 In an earlier module, I talked about these three checkpoints between the phases, called the
Design Advisory and Design Gates.
00:00:26 These design Gates, or D-Gates, are checkpoints for the project team to make sure there is a
consistent and delightful experience across the process for the end users.
00:00:36 After you complete each phase, you will work with a team of design experts who support the
success of the user experience and give unbiased advice
00:00:44 on ways to make the interface simpler and more valuable to the end user. They help make sure
the user interface fits in with the process
00:00:52 and works across different devices. You'll see your project continue to evolve and grow with
each D-Gate.
00:00:59 Now let's talk about some of the tools that we use during the SAP Leonardo design-led
engagement process, especially during these Design Gates.
00:01:09 First, we have SAP Build, which has several key functions we use throughout a Leonardo
design-led engagement.
00:01:17 Create low-fidelity and high-fidelity prototypes in Build. You can do this from scratch, or you can
use one of the pre-created templates in the Build gallery.
00:01:27 Then get feedback about your prototypes from users with Build's user feedback study features.
We recommend using Build to host your projects and conduct Design Gate reviews with experts.

00:01:38 Build even has a learning section where you can refresh your skills about the Leonardo design-
led engagement process.
00:01:46 We've also talked a little bit about SAP Fiori, which are our user interface guidelines we use
when we develop products.
00:01:53 Now let's experience SAP Fiori so we can understand the value of using it in our Leonardo
engagement.
00:02:00 What is SAP Fiori? It is the new user experience for SAP software across the enterprise.
00:02:09 SAP Fiori provides a personalized, responsive, and simple experience that reflects the way you
actually work throughout your day.
00:02:18 Meet the innovative concept, the simple design, and open technology that make it possible. The
unique concept puts the user at the center,
00:02:30 disaggregating traditional software applications like CRM into relevant tasks and activities for a
seamless experience across devices.
00:02:40 The elegant design allows intuitive interaction patterns and features a modern user interface for
a hollistic experience.
00:02:49 SAP Fiori also embraces standard open technology and separates the user interface from
business logic.
00:02:57 As technology advances, SAP Fiori can therefore take full advantage of new standards and
trends to deliver a fresh, consistent experience.
00:03:08 Are you eager to improve productivity, increase adoption, and decrease training costs so your
business can run more efficiently and effectively?
00:03:18 Focus on your users, and run simple with SAP Fiori. This wraps up our Design Gates and tools
module.

9
Section 6 Unit 2

00:00:10 Welcome back, and thanks for joining me for this next module where we're talking about the
Design and Prototype phase.
00:00:17 We'll have Gerhard Gellner, another member of the SAP Design Team, share more about the
Design and Prototype phase.
00:00:25 OK, I'm Gerhard. I want to introduce you to the Design and Prototype phase, which is the
natural phase directly after the Discovery phase.
00:00:35 So we are coming from the participatory design workshop where customers, and from the
customer side end users, business users, IT,
00:00:46 and from SAP the specialists from the architecture, from the technology, from the cloud platform,
are working, or have worked together very closely,
00:00:56 designed together the to-be process and also the screen samples. With that wonderful artifact,
which is a joint activity from a 2-3 day workshop,
00:01:08 depending on the scope and on the needs, we take this artifact and want to present this in a
Design Advisory session
00:01:20 to the global design team, to the Build team, and especially also to the SAP internal subject
matter experts to get their understanding, their feedback on the outcome, to understand the next
steps,
00:01:40 and to ensure the viability, the desirability, and, very important, the feasibility of the planned
solution. After that session, our designers know exactly, together with the customer engagement
lead,
00:02:00 what needs to be tracked during the next 2-4 week design activity. How does such a design
activity look like?
00:02:12 Typically, we have set up already from the beginning regular sync points in our calendars and in
the calendars of the business end users
00:02:24 where we want to engage with them and get feedback on the current status of the prototype. So
that means in that design phase we are transferring the paper prototype
00:02:40 into digital form via Build. In that week, and in each week we also have a management meeting
00:02:54 where we present the activities of the current week, what we have achieved, and also we predict
what we plan to do for the next week.
00:03:06 And very important, we have there also the possibility to address topics to our management to
drive our engagement in a very solid and high-value way,
00:03:22 for them, and also for us at SAP. Doing this builds up trust in the development team, in the
design team,
00:03:34 and I have never had a bad experience regarding the feedback and so on. So you have the
capability to address very early critical, interesting points,
00:03:47 and also the customer has the opportunity to bring up immediately their thoughts and
everything, and you can engage and drive this together as one team, as a partnership.
00:04:00 So after several iterations and, as I mentioned already, the 2-4 week engagements we narrow
the design from the mindset, from the ideas, from the thoughts
00:04:15 via the paper prototype into the digital, clickable design prototype, and we are fulfilling more and
more the business needs and the end users' needs.
00:04:29 And this all with our own Build tool, which is built by the SAP Design Team. This has a huge
benefit for us. First of all, we get direct support by the Build team,
00:04:45 if we have some trouble to visualize this via the tool, and they get strong feedback from our side
to understand what they need to deliver during the upcoming weeks and months
00:05:04 to enable us to be fast and more efficient, and also that our customers benefit from this
development.
00:05:17 After many iterations we nearly have the final, clickable design prototype, and we send
invitations to a Design Gate 1,
00:05:32 where the global design team will look at the visual designs and give us additional hints,
thoughts, and so on,

10
00:05:45 so that we can deliver the design in high quality, independent of who is delivering the design.
We can ensure from the SAP side
00:05:56 that our customer has a solid, coherent look and feel which fulfills the Fiori guidelines. After D-
Gate 1, we are ready to hand over this clickable design prototype
00:06:15 to the management and to the business of our customers, and then they have the huge
opportunity to verify with their whole business units worldwide
00:06:28 the clickable design prototype in terms of how they will work in the future with those new
capabilities, with those new processes,
00:06:39 and collect the feedback via the Build tool again. So the Build tool is the central tool from the
very beginning,
00:06:49 from the Explore phase via the Discover phase, via the Design and Prototype phase, up to the
Deliver phase. Thank you.

11
Section 7 Unit 2

00:00:11 The Deliver phase is where we take our high- fidelity prototype and validate it with the
architecture outlined with the customer.
00:00:20 This proof of concept is also validated with end users and business stakeholders to make sure
we're still solving the design challenge at hand.
00:00:28 Finally, we check the feasibility and viability of the project. This aspect of the design-led
development process is usually conducted with our Consulting Services teams
00:00:40 like Custom Development, Digital Business Services, or the Business Transformation Services
teams.
00:00:48 Let's learn a little bit more about the Deliver phase from Gerhard Gellner, who's also a part of
SAP Design Services.
00:00:57 Hello. This is Gerhard. I want to introduce you now to the development phase after we have
started with the exploration exercise,
00:01:06 with the Discover phase, with the Design and Prototype phase, and now we are moving to the
development phase, after we have handed over
00:01:16 the clickable design prototype to the business and they got the great chance to verify this in a
very early phase with their business worldwide, if necessary.
00:01:27 Collecting this feedback - and therefore we are using the Build tool - we are able to iterate with
the feedback on the clickable design prototype
00:01:38 and make it more mature, if it is necessary. Or we can also move on directly to the development
phase.
00:01:45 In that development phase, we have the development architect or development lead as a
leading position together with the customer design engagement lead,
00:01:56 and both are driving this phase together: one from the development side, the other in the role of
trusted advisor already now,
00:02:11 after some weeks, and working with the management. The development units are typically set
up with front end and back end developers,
00:02:21 with machine learning experts, data analysts, depending on the scope, and of course also with
designers,
00:02:27 who are still responsible for the interaction design and how the UI needs to look like. Especially
for the UI, it is important that we can guarantee during D-Gate 2
00:02:44 at the end of the development phase that everything the customer has seen in D-Gate 1, as a
clickable design prototype, is more or less very near to the real developed solution
00:02:59 and connected with the back end, ideally. After they have developed this application in a very
iterative way as the design was generated
00:03:10 via a joint development method where, after each sprint the content gets verified and tested.
00:03:20 We will finalize the testing with common internal test activity of one day, for example, where the
customer design engagement lead, the dev lead, the designer,
00:03:35 they all sit together and test this application regarding robustness, regarding security, depending
on the scope and what was agreed up front.
00:03:45 Afterwards, we send invitations to an external testing together with our customers and our dev
team, and the designer, so that we all get a common understanding
00:03:57 regarding the maturity of that application. And then the customer can decide how to move on the
implement this application and set it live,
00:04:10 or go for a deeper and wider application after they have been totally convinced that the SAP
Cloud Platform is the right tool, that the new approach,
00:04:23 working in a totally different way, is the way to go for the future. And they of course have seen
that they already got after twelve to fifteen or sixteen weeks
00:04:37 an implemented solution, application, on their cloud platform, with the great opportunity that they
can leverage SAP's newest technology,
00:04:51 connect this to the back end, to SAP systems and non-SAP systems, and bring fast value to the
business and their end users.

12
00:05:03 This also gives the IT of our customers huge new opportunities to deliver fast value. And, very
important, the one team approach.
00:05:14 On the customer side, IT, business, and end users who have typically never worked together
before in a project, together with the SAP experts:
00:05:25 We made the unbelieveable happen. Using the capabilities of SAP regarding technology and the
platform,
00:05:36 leveraging the new skillsets of designers, of data scientists, of machine learning experts, and so
on, and using a new end-user-oriented process to experience and develop a new application,

00:05:56 this is the real value. And at the end, we, SAP get seen more and more as the innovation
partner of the future for our customers. Thank you.

13
Section 7 Unit 4

00:00:08 Now that you've learned more about the process, tools, and roles involved in a Leonardo
design-led engagement, let's review and talk about next steps.
00:00:18 Here's a quick recap of what we covered today. For Leonardo engagements, we are using the
proven design-led process
00:00:25 to co-innovate with our customers. To create and manage prototypes, we recommend using
Build
00:00:31 for all of your design and project needs. Remember that your prototype will be evaluated by Fiori
experts,
00:00:39 so it's essential to follow the SAP Fiori user interface language. These evaluations of your
design are called Design Gates,
00:00:48 and they ensure your prototype is adaptable, simple, and delightful for your end user. If you're
ready to dig deeper into the Leonardo design-led engagement process
00:01:00 you have a few key resources to find more information. The SAP Leonardo product page
frequently updates with information
00:01:08 about technology capabilities, accelerator launches, and customer success stories. Now, are
you interested in becoming a part of an SAP Leonardo design-led engagement?
00:01:20 Talk to your manager about the requirements and potential role you want to have as part of a
project team.
00:01:26 SAP offers training for customer-design engagement leads and design experts, for employees
and partners.
00:01:33 Thank you so much again for joining me on this journey to learn more about the SAP Leonardo
design-led engagement process.
00:01:41 Now let's continue to identify and solve today's business challenges using this human-centered
approach.

14
www.sap.com

© 2017 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or
for any purpose without the express permission of SAP SE or an SAP affiliate
company.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an
SAP affiliate company) in Germany and other countries. Please see
http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional
trademark information and notices.
Some software products marketed by SAP SE and its distributors contain
proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any kind,
and SAP SE or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP SE or
SAP affiliate company products and
services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be
construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue
any course of business outlined in this document or any related presentation,
or to develop
or release any functionality mentioned therein. This document, or any related
presentation, and SAP SE’s or its affiliated companies’ strategy and possible
future developments, products, and/or platform directions and functionality
are all subject to change and may be changed by SAP SE or its affiliated
companies at any time
for any reason without notice. The information in this document is not a
commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and
uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these
forward-looking statements, which speak only as of their dates, and they
should not be relied upon in making purchasing decisions.