Code coverage with Coverlet for .NET

Code coverage measures how much of your source code is executed while tests are running, the measurement result is represented in percentage, and one or more coverage criteria are used as rules which…


独家优惠奖金 100% 高达 1 BTC + 180 免费旋转

Prototype the right solution

It looks like we are almost reaching the end. However, there still exist many details we need to review, and polish our solution. Although I met an excellent group I believe, the most perfect group still cannot make everyone have the same understanding of one project. If a group only composes the words, each group member will have their own image of the words. I guess that is why we need a prototype at this stage.

I agree with Tom Kelley who is the partner of IDEO on defining prototyping as a language. If typing the letters to deliver and communicate is the most accessible way, I would like to say prototype is the most straightforward language. By prototyping, your co-worker will get your idea immediately; your clients could give the more practical request after viewing the prototype; and you as a designer would know whether it is the correct solution or not.

In the class, our group talked about what’s the difference between user journeys and prototypes. I believe this is a crucial discussion, which lets my group make sure of the direction of the prototype. At the very first, we always focused on the details, like what the reception desk should have, what type of Apple Tech we should include and what kinds of changing rooms are better for users, etc. Those questions are good, however, I think those are what we should think about under the user journey step not under the prototyping step. For the user journey, we can stand on the user’s feet and think about all the details that improve the user’s experience. For a prototype, we should design the solution from a holistic view. For our pop-up health center project, we should think about where to make the ‘user journey’ happen.

By reading the Roadmap of Prototyping, we got that our first step is clarifying the purpose, selecting our design method and then thinking about how to measure the prototypes. Following the previous steps, here we need to generally explore the design space, we need to visualize our solutions. Due to the constraints, we decided to prototype our solutions on Figma. We plan to use Figma to simulate the design in reality. With the exception of Dan, none of us had any experience in prototyping. So we agree on ‘1 person 1 prototype’ , and then combine our prototypes. We hope by this way, we could try something new but not reduce the quality of our group’s prototype. Here is mine ~

I am not sure whether this is a typical prototype or not. What I want to do is designing the whole pop-up space where we could help our users solve the problem. As you can see, finding references is useful for me to deliver my image of Pop-up Health Center. And I think my teammate will get my ideas easily by looking at the references.

What we need to do next week:

And then… What is the next step?

Add a comment

Related posts:

Telling a story through multimedia

Since my last journal post, I have conducted my final interview for this story on the rock climbing and how its entered mainstream health and wellness in San Diego. The interview took place inside of…

They believe to understand the world

If some behavior is not appropriate, they do everything to make it similar to their one, without considering the differences, indeed annihilating them. They have endemic insecurity combined with the…

3 Surprisingly Simple Steps to Help Make Your Bad Days Better

What to do when you have a bad day? Sometimes, you hate everyone, everyone hates you, and your head hurts. Here are 3 simple steps that help.