Name Card - Mission Reflection

1) Why is each step required?
Empathize was needed so that I could know what the user wanted from the namecard.
Define was needed so that I could give myself a theme as a starting point for ideas of my namecard and know what challenge I should focus on.
Ideate was need so that I could sort out my ideas and pinpoint a final one that I wanted to make.
Prototype was needed so that I could actually make the product.
Test was needed so that I could get final feedback on my product and know what I could improve as a whole.

2) I learnt that what I was imagining for a name card was different from what the user wanted so I had to change my thinking to his and her thinking and I learnt that I needed to keep asking for feedback so that I could get exactly what the user wanted.

3) My name card is disruptive because it does not show the boring things that people want but the interesting details that the user actually wants.

Name Card - Prototype/Test

Feedback:

Kenneth: It looks cool. I like the font of your name and the hummingbird.
Delaney: It looks really good.

Name Card - Ideate

Ideate Feedback:

Delaney: It's good.
Kenneth: It's looks great.

Name Card - Define

Theme: Water and Nature

Challenge: Expressing the horoscope and what it means

Name Card - Empathize

I am making a name card for Kenneth and Delaney.
My name card will have my information.

Favorite color?
Favorite sport?
How old are we?
Dream vacation spot?
Name?
Favorite activity?
Favorite Animal?
Favorite band?
Horoscope?
Favorite movie?
Which of the elements are you?
Spirit animal?
Favorite book?


Digging Deeper:
Name?
Vacation Spot?
Color?
Favorite band?
Horoscope?
Which of the elements are you?
Spirit animal?

Software Development Life Cycle and Design Thinking Process

Software Development Life Cycle:

• System Analysis, requirements gathering: Defines project goals into defined functions and operation with the objective in mind. It is the process of gathering user requirements, diagnosing problems and recommending improvements to the future system.
• A series of steps followed by the developer are:
• 1) Gathering Facts: End user requirements are obtained through documentation, client interviews, observation and questionnaires - asking what the user is currently doing and if there are any specific improvements they want or prefer.
• 2) Scrutiny of the existing system: Identify pros and cons of the current system-in-place, so as to carry forward the pros and avoid the cons in the new system.
• 3) Analyzing the proposed system: Solutions to the shortcomings in the step two are found and any specific user proposals are used to prepare the specifications.
• System Design: Describes desired features and operations in detail, including screen layouts, rules, guidelines, process (data flow and entity relation) diagrams, pseudocode and other documentation.
• Development: The real code is written here.
• Integration and testing: Brings all the modules (pieces) together into a special testing environment, then checks for errors, bugs and interoperability.
• Maintenance: During the maintenance stage of the SDLC, the system is assessed to ensure it does not become obsolete. This is also where updates are made to the initial software. It involves continuous evaluation of the system in terms of its performance and completing the change requests based on the feedback.

Design Thinking Process:

Empathize: Work to fully understand the experience of the user for whom you are designing. Do this through observation, interaction, and immersing yourself in their experiences.

Define: Process and synthesize the findings from your empathy work in order to form a user point of view that you will address with your design.

Ideate: Explore a wide variety of possible solutions through generating a large quantity of diverse possible solutions, allowing you to step beyond the obvious and explore a range of ideas.

Prototype: Transform your ideas into a physical form so that you can experience and interact with them and, in the process, learn and develop more empathy.

Test: Try out high-resolution products and use observations and feedback to refine prototypes, learn more about the user, and refine your original point of view.

Help me remember someone's name

1) Ask their name
2) Remember appearance and where and why I met them to correlate with the name
3) Use their name often when talking to them
4) If you put the contact in your phone, put a picture and notes in the contact
5) Get information about them so the person seems like more of a person than just a name.