Build Your Own SAP Fiori App in the Cloud
Por: claytonmneves • 10/5/2016 • Ensaio • 12.323 Palavras (50 Páginas) • 454 Visualizações
openSAP
[pic 1][pic 2]Build Your Own SAP Fiori App in the Cloud
WEEK 2, UNIT 1
00:00:11 | Hello and welcome to week 2, unit 1. I'm glad to be back with you. |
00:00:16 | This week is all about design and design thinking in the context of SAP Fiori. |
00:00:22 | So one thing I'd like to make clear up front. Typically the design process is quite collaborative |
00:00:28 | and what I'm about to share with you is often presented in more of a workshop format |
00:00:34 | where, ideally, there are team breakout sessions and lots of collaborative processes involved in brainstorming and whiteboarding. |
00:00:41 | However, for the purposes of this course, I'm going to present to you design thinking in a way that allows you to jump right into the process on you own. |
00:00:50 | Just know that in the ideal case, design thinking is quite the team effort. |
00:00:55 | So. Before we get too far, let's define design thinking. |
00:01:01 | As you can see here, design thinking is a design methodology all about creating innovation by combining diverse people, creative space, and an iterative approach. |
00:01:13 | The idea is that seemingly complex problems can be addressed effectively if broken down and iterated upon. |
00:01:21 | Ideal solutions and successful products generally have three things in common. |
00:01:27 | They are equally feasible from a technical point of view. The “Can we do this?” feasibility circle is sometimes also referred to as the technology circle. |
00:01:38 | They are also viable from a business point of view, so viability is related to business value. |
00:01:43 | And finally, they're desirable and attractive from a human point of view. |
00:01:49 | So the goal is to balance desirability, viability, and feasibility, also known as human, technology, and business aspects of design. |
00:01:59 | So design thinking is meant to be a holistic, outside-in perspective that helps you to understand the goals and the needs of your end users, |
00:02:07 | customers, and other stakeholders in a way that balances these three spheres. |
00:02:12 | And as you'll see more and more, one of the characteristics of design thinking is to rapidly come up with non-coded stories and mockups that illustrate ideas and drive conversation. |
00:02:24 | This can help validate solution concepts with end users as well as with technical experts. |
00:02:30 | One last point here. Notice the “Start here” pointed at the desirability. This is on purpose. |
00:02:37 | Because of the three spheres, desirability is often the most overlooked. |
00:02:42 | It's much easier for a technical dev person and a business person to get together and determine what's needed. |
00:02:49 | But don't underestimate how important it is for the actual end user to want what you think they need from the app you're creating. |
00:02:58 | So this leads us straightaway into a quick snapshot of how different roles approach app creation from different angles. |
00:03:05 | Try to keep this in perspective and take into consideration the often competing angles. Everyone wants to deliver a great app, even if a developer lead is focused on technical feasibility, |
00:03:16 | whereas a product manager is focused on what's needed for business value. |
00:03:20 | But again, try and think like a designer as much as possible. This is often the forgotten perspective. |
00:03:27 | And remember that it's equally as important to make sure an app feels great and is desirable to use by end users. |
00:03:35 | So let's take a look at a birds-eye view of the design-thinking process. There's the problem space and the solution space. |
00:03:44 | It's best to start broadly and narrow in the focus later after iteration. Think of the problems you would like to address by creating an app. |
00:03:54 | What are you trying to accomplish? Try to create choices. This is called diverging. So don't hold back in this section. |
00:04:01 | Map out all the problems you can think of related to the scenario you are trying to address. |
00:04:06 | Then make some choices. Weed out the symptoms and converge upon the real problem you want to address. |
00:04:12 | Next is the solution space. Now that you have a problem you are addressing, you diverge. You brainstorm tons of ideas on how to solve that problem, |
00:04:21 | take a break, and then you come back and converge. That is, you analyze all the solution options you came up with and determine the best one that most effectively addresses the problem identified. |
00:04:32 | I know this is sounding a bit abstract at this point, but it's important for you to be very aware of this methodology before we go into some specifics. |
00:04:40 | In unit 3 of this week, we'll go through an example of this process within the context of Fiori. |
00:04:46 | For now, just know that the problem space and the solution space both are equally important and require you to diverge or create choices and then converge or make choices. |
00:04:59 | Here's another view of the design thinking process. Notice the two broad categories represented by the two large circles. |
00:05:06 | It's representative of what we just talked about earlier: the problem space and the solution space. |
00:05:13 | This shows you how much you have to iterate within the process. You often need to go round and round in one space before you're ready to move on to the next space, |
00:05:24 | meaning when identifying what you think is the problem you're solving for, you have to do your research. You need to interview all of the relevant stakeholders, |
00:05:33 | most importantly the end users, but also business owners and technical experts. |
...