My name is Melissa Powel, and I'm the Global Program Manager for Design Expert here at Google
I am currently running the global program for design expert
And I also teach the Sprint Master Academy externally within the community
And it's a personal passion to spread best practices around collaboration
because I believe that together through business design and engineering
We can work together to create incredible products
I'm extremely inspired by the community in the work that they've done to hope both within around teams
And with the startup community in general, and I'm excited to see where the future goes
What do I think about human centered design
Human centered design is critical to any product that is meant to have human as a user
And all to after meeting about amazing technology isn't the power that they can do
Or we falling love with some of our UI or pixels
And we're not thinking about the user the end in the day
Design thinking and design sprint specifically hopes we frame the challenge
In terms of the user what the user really cares about
And helps people build products, then make peoples lifes better
Can you tell more about the design sprint and design thinking?
The design sprint is a 5 phase framework
That incorporates the best practices from business design and product strategy
And it helps people focus first on the problem before jumping into the solution
Our brain are wired to solve problems
We have to sometimes react quickly when we were confronted with an issue
But the design sprint helps slow that processes down
At the beginning so you can focus on solving the right problem
When we solve the right problem, we can be sure that our solution is correct
What you've been doing with the design sprint here at Google?
Internally at Google, teams have started to adopt the design sprint methodology across the board
Particularly in last 4 years we've seen a lot of momentum around using the methodology
Because it saves people a lot of time
I remember hearing from one of my colleagues saying that they've been working on a projects for six months
And after those six months they discover the an issue, a products that made, the project canceled
This could've been of waited had they spent more time, unidentified the problem they were solving
And making sure, that the solution they were creating was the right one
And, it also allows for teams that are working globally
To come together, and align on one specific vision
And run the design sprint with the global team working out of 3 different offices
And in order to kick off the project and then sure that we were able to make a very tight deadline
We had to run a design sprint, align ourselves, and when we came back to our home countries
We knew exactly what everybody was working on, and we were align on the same vision
Running a design sprint is different when your inside a large enterprise versus when you had a startup
I mean a large enterprise, the biggest challenge just making sure you have stakeholders in the room
And specifically if you have people or decision makers who can't be present for the entire design sprint
Which happened frequently, I make sure they have them joined in at the specific time in the sprint
Particularly from most of the understand phase in the very beginning
And then threw out at the end of each day for the sub-sprint days in the sprint
That way when the team gets back and talks to the decision maker
They realize that their all align on one vision
And the stakeholder isn't going to say "No ain't, that was never part of my vision
I'm not gonna approve that, approve that, let's go back to what I originally told you to do."
In startup I think that the challenge is time
So if your concern about running in design sprint whether not is really the right thing to do
I don't thinking design sprint solves every problem and Sometime running your business as usual is okay
But if you continuously come to the same problem over and over again
And you're getting the same problematic results, you'll want to stop, get everybody together
And really put your heads down and try to solve the right problem
That's when I think that is worth your time, and you'll end up saving time rather than wasting it
If you'll going listen to Kai Haley's talks from Google I/O
You'll hear how she has used design sprint to flax, to meet the needs of her team and schedules for her team
The question we've often get is: Do you have to run off 5 days sprint?
If you talk to Jake Knapp or if you read his book you'll see that the statistically speaking
He's run many many different links of sprints, and he's found that 5 days is the perfect demand of time
Now you've had in-depth talks with him about my theory around the duration and what these 5 days mean
And the short answer is you can adjust the link that the sprint to meet the needs of your team
Just be aware that if you shorten the sprint to 2-3-4 days
Any work that you're not completing with your team, will fall onto you
So while you running a sprint, you have all 5 people were committed to solving the problem
Working together, documenting, and finalizing prototypes
Anything that happens outside of that sprint, is likely gonna drag on a little bit longer
It's gonna fall on onto one person a little bit heavier
You not gonna get the collaboration that you get in those 5 days
That said the majority of the sprints that we run within the community, run between 2 to 4 days
And I'd say that 4 days is a very very calm and efficient way to run a sprint
And it'll last for 1 day for recovery and recap
But often 4 days is still to much, and so would even running in 2 or 3 days sprint can make a lot of leeway
To solving the problem
Another question that we often get is, How often should I do run the design sprint?
Should I running design sprint every single day? Should I run more than once a year?
Is it only for the beginning of the sprint or only for the beginning of a project?
And to this I said depends
Depends on the size of the problem, it depends on how well your current flow of work is effectively solving your problem
I was talking to a product manager here at Google and he said there was one year
That his team ran a different 4 days design sprint every week for the entire year, without breaks
This is obviously not something that every teams able to do
Where I would recommend is that you should run a sprint when it make sense for you
And some of the indicators that you might have that the design sprint is necessary
Is your heading the same problem over and over again
Or perhaps you have a global team, and you need to align on one single vision
Or if you have a very very tight deadline you need to inject speed
And you having trouble finding the right direction
Design sprint is very effective at giving you focus
So I would recommend is that you run a sprint, when the need calls for it
Not just because it's something that you heard of before in it, sounds exciting
It does take a lot of time but it's very effective at helping team focus and helping you solve the right problem
Another question we often get is, What happens when you go through the understand, sketch, decide, prototype, and validate stage?
And you realize when you validating with users, that you've created something that people don't want
This is a great place to be
Rather than waiting a couple of months before finding this out you now know within 5-4 sometimes 3 days
What do you do?
So sometimes you can take that information you know have a very solid understanding of your problem
You can take this information and jumping to a second sprint very quickly
Rather than starting from the understand phase
Start from the sketch phase and go right into sketching, deciding, prototyping and validating again
This way you can leverage the information you have and keep up that fast momentum that the sprint allows you to have
Sometimes people want to know
I'm not a designer, what should I do when at prototyping day?
And during the prototyping phase there's actually a lot of work to be done
I would recommended you to divide your team up to divide and conquer the task in the end
The top 3 roles that you can have is prototyping during the visual design
You can also do documentation, and finally you can prepare for the user interviews on the final day
In addition to those pieces you can assign somebody to be a copywriter for what's going to appearing the UI
And you can have somebody - maybe stitching everything together to make a seamless one piece
Design is an art
And sometimes eight hours doesn't feel like enough time to complete the prototype that you comfortable putting in front of a user
But my favorite quote from the user researcher here at Google is "The fidelity of your idea should match to fidelity of your prototype.
You shouldn't be spending more than eight hours during in design sprint, because you not certain about the idea."
I know that it's difficult to put that level of fidelity in front of an external user
But is really important that you validate quickly you validate early
If you need additional time I recommend you do it overnight
So that you keep the pressure on yourself and on your team to meet the original deadline of one day
Google does a lot of efforts to try to educate developer communities on Google technologies
And raise the technological bar around the world
But I think that is really important to also share learnings about how to make those products really valuable to users
If I wanna create a world that is filled with solutions that I'm proud to be part of
I want to help create a future that's brighter tomorrow
And so through that I think one of the keys is collaboration and design sprints is one piece to that puzzle
If your interested in running in design sprint I recommend that you reach out to Dr. Eunice Sari
Whose certified Google Certified Sprint Master or you can go to developers.google.com/experts
And search for certified sprint master, you can find other local experts who can share some other knowledge
We're providing additional links for self-serve platforms where is you can learn yourself with free resources
On how to run a design sprint for your team, thank you
For more infomation >> Lean UX for Product and Service Innovation 2017 - UX Indonesia - Duration: 1:59. 
For more infomation >> Content Strategy for Digital Products and Services 2017 - UX Indonesia - Duration: 1:32. 
For more infomation >> Tech World: Uber's colossal hack, a $1.8bn court battle and more - Duration: 12:45. 
For more infomation >> Cómo preparar unas sencillas galletas de Navidad - Duration: 5:50. 
For more infomation >> how to make a create new gmail account in bangla(কি ভাবে জিমেই একাউন্ট খুলবেন)!! - Duration: 7:38. 
Không có nhận xét nào:
Đăng nhận xét