Read the article below, and compare the wording and techniques to requirements e

Question

Read the article below, and compare the wording and techniques to requirements engineering. Write a 2 - 3 paragraph summary. Is there similarites or differences?

Why Great Experience Design Starts With A Story

Sometimes, words are worth a thousand wireframes.

Every experience design firm uses a set of common tools to begin the process of uncovering design opportunities. First, we perform or review user research to understand who the users are and why the experience will be important to them. Second are personas. This process of fleshing out a personality and context on top of the normally generic demographics found in a basic target audience profile can certainly help everyone on the project envision themselves in the user’s shoes, so to speak. Also included are user journeys — the detailed, step-by-step accounting of how we get a user from Point A to points B, C, D, etc.

At our firm, we’ve built another step into our initial ideation process: We write stories. These stories are detailed narratives that walk through the user journey, step by step but annotated with context, motivation and expectation. Why take the time and effort to add this extra step? Because it has helped us to more quickly and effectively create truly unique and delightful user experiences. How so? Read on.

Stories convey vision without undue influence on design.

You can’t unring a bell. And likewise, it’s nearly impossible for a designer to unsee a sketch or wireframe when it comes time to imagine a radically new user experience. During the initial ideation and brainstorming phase of development, a well-crafted story can convey all required or desired points of interaction without unduly limiting a designer's imagination.

By nature, when hearing a story, we all begin to picture the missing details of how the explained action might manifest in physical form. And a talented designer, without the prior influence of a set of complex wireframes, will more often than not envision something elegant and simple. If their vision is incomplete, ultimately requiring the inclusion of greater detail or functionality, they are at least starting from a vision with a level of elegance they are inclined to protect.

Stories document emotional expectations.

If a technical spec conveys how an experience should be physically coded and deployed and a functional spec conveys the interactions that code should facilitate, a story can be thought of as the emotional requirements documentation. What points in the user journey should elicit joy or delight? What points require thoughtful decision-making? Which offer relief?Stories can present experiences unconstrained by technology limitations.

All references to his infamous “No one will ever need more than 640K of RAM” quote aside, Bill Gates has always directed his developers to code Windows for a level of computing power and speed greater than they had available to them at the time. He knew that Moore’s Law would catch up at some point. Likewise, you can, in the process of storytelling, envision a radically disruptive user experience that may seem to be beyond currently available tools or resources. And we’ve found that if you can create a compelling vision, technology eventually finds a way.

Storytelling forces prioritization.

Creating any successful narrative is an exercise in prioritization. The author needs to provide enough detail to paint the full picture, but not so much that the reader gets bored — or worse, overwhelmed. When done successfully, the story is a roadmap for the visual hierarchy to come in the final UX design. Those interface items or experiences that are critical to forwarding the narrative should, in theory, be featured more prominently in the final UX design. Those elements that are unnecessary to the story should be minimized or considered for removal entirely.

Storytelling exposes the holes.

Frequently, the first thing out of developers’ and UI designers’ mouths after looking at a functional requirements document is, “How’s that supposed to work exactly?” The simple act of clearly describing a user’s journey through an online experience forces the author to resolve abstractions in the requirements.

Let’s say “search functionality" was required to be a function presented to the user. The story should describe what the user was searching for, what they were hoping to find and how they viewed and refined their results. More importantly, the story should show how the presentation of those results forwarded the user’s goals.

For example, how were the search results initially prioritized (e.g., by subject relevance, by date of creation, price, custom taxonomy, etc.)? And finally, the story should explain why that prioritization mattered on a personal level to the user. To a UX or UI designer, for example, it gives them a place to start, a more linear problem to solve and an understanding of the emotional reward the experience can provide to the user. Further, to a database designer, the story could imply what data types, connections or facets must be accounted for in the database schema.

If you can’t explain it to a 6-year-old …

Simply put, the act of creating and communicating a story that every team member can understand and follow forces clarification of thought. In the best case, the story will inspire the exploration of new ideas, untethered by perceived organizational or technical constraints. And ultimately, if you share the story and the majority of your team members or clients don’t respond with something to the effect of, “That sounds cool,” the end product probably won’t seem so, either.

Explanation / Answer

After reading the article, it is clear that there is similarity in every heading of wording that story telling has many associated benefits in engineering or innovative design. It helps to simplify the concepts to even an illiterate person. For example: Who will forget the story of James Watt, Great Sir Isaac Newton etc. After knowing these stories in class, many great scientists of today were developed the scientific temper in them.

A modern organization might uncover opportunities to design new product with its Stories that convey vision without undue influence on design. It might be possible that users match their expectations with the related design or product offered by the organization easily. When stories will be target the emotions of the users’ then technology get sharper design which fulfils the basic or actual needs of the end users. Vision and technological advancement must get an alignment. People don’t need to fly themselves so it should be tapped within the reality of design or implications.

The importance of storytelling is that it offers prioritized the set of activities to design. It revel the untapped areas in terms of technological up gradation and setting the milestones. It should be so simple that even a small child can understand that what will be the NASA want to do by its curiosity rover.

Related Questions

Navigate

• Browse (All)
• Browse R
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.