Tag: persona

Being Awesome, Empathy, Micro-Patterns, Motivation, Persona

Why Do We Search For Identity?

Posted on by GFandBA

Growing up, I was a fan of the San Diego Padres baseball team. Well, specifically Tony Gwynn, but the Padres came with him. There have been years where I watched them trade away quality top talent, in hopes of landing a large quantity of moderate talent. Why have one 5-star player, when you can have three 2-stars? So when a team I loved had replaced every player at every position with new players, were they still “my team”?tonygwynn

This is the crux of the thought experiment raised by Plutarch. Not Hunger Games Plutarch; I’m talking about ancient Greek Plutarch. He wanted to know when the Ship of Theseus stopped being the Ship of Theseus, if it was replaced with replica parts, one by one. You can check out a discussion at Brain Pickings.

At least make sure you watch the video in the Brain Pickings article, which can also be found here: Who Am I?

Humankind asks “Who am I?” At least since we’ve been able to think these types of thoughts. There may be some earlier humans who never really contemplated their place in the universe, or if Oog and Thag talk about them when they’re not in the cave… I digress.

Both the video and article are fantastic for explaining what is at the heart of the conundrum. However, I want to know what’s at the heart of the human. This leads me to a different question.

Why do we ask “Who am I”?

“Who am I?” gets at identity. I want to understand why we question it. I am going to spoil the end of this post and tell you right now, I don’t know. But it does generate interesting questions that need to be explored. Surely, some folks have explored one or more of these. I want to to talk to these folks. If you are one of these folks, let me know! I want to talk to you.

Questions

  • Is who we are different from time to time? From place to place? From situation to situation?
  • Is “Who am I?” even what we want to know?
    • Should it be “Am I being who I want to be?”
    • Should it be “What’s my place in the universe?”
    • Should it be “Who do others think I am?”
  • Do people with extreme levels of self-confidence ask “Who am I?” (extreme = really high AND really low)
  • Does “wearing many hats” fragment our identity?
    • Why can’t we be the same person and keep our identity whole?
    • Are the forces on the need for “many hats” external or internal?
  • Does finding an answer to “Who am I?” solve anything?

One Last Thing Before You Go

This search for identity generates a new-to-me connection. Our inability to satisfyingly answer “Who am I?” leads to a void that “things” have been able to fill.  If I buy a cat, I open the door to becoming a cat person. If I buy activewear from Nike, I showcase my athletic identity. Heck, you can’t even properly root for the Padres without buying some team gear. Maybe that’s part of how we cement part of our identity answer.

“Who am I? Well, I got all these Padres hats and shirts, so clearly I’m a Padres fan.”

It feels like those are the easy answers to what is supposed to be a deep and soul-searching question. “Who am I?” sounds like a status report on the path to the ideal you want to achieve.

But still, I gotta know, why are you asking?

0
Being Awesome, Empathy, Going Forth, Innovation, User Experience

Making Customers Feel Cool

Posted on by GFandBA

coolCurves are the enemy of fast moving trains. Just ask Denzel Washington and Chris Pine in Unstoppable. Nearly 30 years before the movie, The British Rail Research Team unveiled the APT. The APT was a train that tested out at an amazing top speed of 160mph, and could safely sprint 40% faster than any other train through curves. And it failed.

In 1981, the first public riders traveled aboard the APT and felt motion sick from the uncommon tilting that allowed the train to rip through the bends. Data, speed, and savings aside, the customers did not feel cool while leaning and the train quickly picked up a nickname. The Queasy Rider.

“If people are made to feel uncomfortable in the kitchen, they won’t go in there.”- Giada De Laurentiis

The APT was technically a marvel, doing something that the long, rigid rectangely trains never could before… lean into the curves like a well-trained sprinter. However it was the user experience that lacked the sparkle. It’s hard to argue how neat it is to go 40% faster when the rider is busy holding onto their lunch. The user experience is a major key.

Design thinking encourages us to find the real root problem for customers, and to evaluate what jobs they need a solution to do. Yet if your solution solves the problem at the expense of user experience, then it is doomed to fail. There is a famous quote by Leo McGinneva, while talking about how customers don’t go to the hardware store to buy quarter-inch drill bits. He said, ‘They don’t want quarter-inch bits. They want quarter-inch holes.” It’s easy to abstract this into a postulate:

Customers aren’t buying products, they are buying a version of their life with a problem solved.

People purchase products because they can make life easier, more enjoyable, more rewarding. This is why medicine comes in flavors now. Why choke down an unpalatable tonic when you can get the same benefits with bubblegum flavor?

It is easy for us to focus on the tangible features when developing a prototype. But it is crucial to bring user experience into the equation as early as you can, and for as many steps possible. There needs to be devoted thought to the future user and making them feel like they’re getting ahead of the game by using your product. Fast Company has a great article tackling the marketing angle of this. In it, Belle Beth Cooper (co-founder of Exist) says “A feature is what your product does; a benefit is what the customer can do with your product.”

“Empathy is about standing in someone else’s shoes, feeling with his or her heart, seeing with his or her eyes.” – Daniel Pink

APT eventually returned in 1984 after some work to shore up the uneasy feeling in the tilt. This time the reviews were much better, but not good enough to save the train. The negative user experience and nickname lingered, and all APT’s were removed from service by 1986.

Think about your project. Is it full of fantastic features but leaving the core customer queasy? Maybe it is time to lean into some user empathy and tilt your solution in a different direction.

After all, our customers shouldn’t just be able to go forth. They also need to be awesome!

0
Going Forth, Innovation, Prototyping

Paper Prototyping as a Creative Catalyst

Posted on by GFandBA

I think we can all agree that Disney Pixar’s newest film, Inside Out, doesn’t merely tug at your heartstrings. Rather it grabs hold with a death grip and shakes them with a vigor that would make the Grinch weep, even prior to his heart enlargement. If you’ve not seen it yet, prepare your “It’s dusty in here” and “I got something in my eye” crying cover stories and go.

As you shed tears for Bing Bong (and you will) think of one simple fact… At one point, this story sucked.

These are the prototype figures I use for games. These have been knights, museum guards, venture capitalists, and more.
These are the prototype figures I use for games. These have been knights, museum guards, venture capitalists, and more.

It was likely long ago, back in the early pitches and storyboarding phases. However, as Pixar Animation President Ed Catmull states “I’m not trying to be modest or self-effacing. Pixar films are not good at first, and our job is to make them so—to go, as I say, ‘from suck to not-suck.’” He adds “We dare to attempt these stories, but we don’t get them right on the first pass. This is as it should be. Creativity has to start somewhere“.

One key takeaway here is that we, as innovators, must start our creative idea somewhere, tell the story, and figure out how to get it “from suck to not-suck”. In fact, the faster we do this, the better. We don’t want to spend needless hours putting all kinds of sheen, gloss, and functionality into that first prototype because we will likely fail and need to pivot. That is why we need to prototype on paper.

I’ve prototyped a few games just as a means to get an idea down, get it moderately functional, and to give the game idea some quick playtesting. I do not want to spend time or money in making beautiful, final quality game pieces because there are still many aspects that will need developing, balancing, or discarding. In order to prototype quickly, I keep a large stack of 3 by 5 notecards nearby (along with shiny glass beads, sparkly sticker books, and a plethora of dice). These become my makeshift game pieces. The best part is, they aren’t limited to prototyping games. A notecard could represent an app’s splash screen, an email template, or whatever you are innovating. There is always a way.

One quick note: Paper prototyping is a method, a way of making your ideas tangible in a quick, low-cost manner so that your innovative hypothesis can be validated. It does not HAVE to be paper, but whatever material you use should have the same inexpensive and recyclable nature.

Let’s take a look at some reasons why you should prototype of paper early, and often.

Notecards! A prototyper's canvas. These could be login screens, user profiles, or cupcake configurations.
Notecards! A prototyper’s canvas. These could be login screens, user profiles, or cupcake configurations.

YOU CAN PROTOTYPE CHEAP

Notecards can be bought for several on the dollar. This definitely beats the time and effort that would go into developing a digital or physical first version of your innovation. Imagine spending resources to have a first iteration of your innovation built, only to put it in front of some customers and find out that your solution needs some big time overhauling. Instead, if you had paper prototyped that primary version, you might be out a couple dollars. That’s a pretty decent Return on Investment for all the learning you can do with a first prototype.

YOU CAN PROTOTYPE FAST

There you are, sitting with a target customer, showing them your idea. You watch them interact with your prototype and you notice a huge flaw that needs to be addressed. If you’ve built a more elaborate prototype, this pivot can be costly and put a huge delay in your deliverable timelines. All those items in your kanban or development pipeline now have to sit and wait for this first one to be addressed. If you prototyped on paper (and remembered to bring notecards and pencils to your focus group) you can mock up the new screen or feature within seconds! Remember that you are just telling your innovation’s story  so these don’t have to be marketable graphics. They just need to be enough for the customer to see how it works and for you to watch them “interact”.  Plus this reduces your iteration time to something very minimal.

YOU CAN BE DARING

When you aren’t worried about cost of developing a prototype, and you aren’t worried about the time it takes to pivot and persevere into iteration two and beyond, then you can be as adventurous with your prototype as you want to be. You aren’t risking a ton of resources so put those ugly ideas out there! Be disruptive, do things the way no one in your industry does them. If your “out-there” idea crashes and burns, all you are out is a handful of notecards.

YOU CAN PUT THE FLOW IN THE CUSTOMER’S HANDS SOONER

This "paper prototyped" game card could represent your target customer's profile or maybe a feature within your innovation. You can quickly and easily make changes.
This “paper prototyped” game card could represent your target customer’s profile or maybe a feature within your innovation. You can quickly and easily make changes.

The best time to learn about your solution’s fit with your customers is when they are holding it in their hands. When your prototype only lives internally, it will always appear perfect. You need to kick it out of the nest and see if your idea can fly on its own. The faster you can do this, the less time you spend on bad ideas. Even if you don’t have it all figured out yet, get your core mechanics on paper and start asking your customers to look at it. It opens up new idea avenues for you to explore and it helps paint a better picture of what jobs the customer needs your innovation to do. We can all work on understanding our customer better, because they are always changing. Opportunities to learn and grow are valuable, especially when your innovation is in the very formative stages of its lifespan.

Later, we’ll go into some methods on “how” to prototype with paper… but for now, grab your notecards and start iterating!

Challenge

  • For this challenge, you will need 10 notecards.
  • Take 6 notecards and prototype the flow your customer will experience with your prototype.
  • Show it to someone and have them “pretend” its the real deal.
  • Iterate right then and there on any pain points they experience. Use your remaining 4 notecards for any additional or replacement steps in the flow.
  • Identify places you need to pivot and persevere and use more notecards to craft the next version!

___________

What materials do you use to prototype with? I’d love to see what is in your bag of tricks down in the comment section.

4
Going Forth, Innovation, Persona, Pre-Mortem, Testing

I’m not dead yet!

Posted on by GFandBA

I enjoy a good scary movie from time to time and zombies are everywhere. Zombies cause a load of difficult situations for folks. Imagine that you’ve just pronounced Steve* deceased, when all of a sudden, Steve sits upright and starts expressing his sudden love of brains. “My bad everyone” you might say sheepishly “I could’ve sworn he was a goner.” Then everyone rolls their eyes at you and it just gets super awkward. If only you had done a little more checking before, you might have a plan for when your “deceased” diagnosis failed.

Whether it is zombies or innovation prototyping, you need to do a pre-mortem.

The whole point of building prototypes and testing them with customers, is to see if you solution succeeds or fails. Yet we often wait to get our “failure folder” before we start thinking of why it went wrong and where the pivot opportunities are. There is no need to wait to make decisions when you conduct a pre-mortem.

Pre-mortems can help you plan if your prototype fails and comes after your brains.
Pre-mortems can help you plan if your prototype fails and comes after your brains.

Pre-mortems occur after your prototype is ready for testing, but before you do any actual testing. They allow you to take a glance at your work from a different angle. To this point, you’ve spent your brain power finding ways to get the prototype to work, how to demonstrate your hypothesis, and how to collect the data points you know are important. A pre-mortem let’s you stop those thoughts, and think “How can this prototype fail during the test and what am I going to do after it does?”

Pre-mortems focus your thoughts of failure to a single test of your prototype, not your end product. By keeping the scope of your vision on just one test, it is way less scary to envision the many ways it can fail.

A simple pre-mortem can be done by yourself as long as your prototype is in its testable state. However, it is very beneficial to have other people look at your prototype during the pre-mortem. These people are not your testers and they may not even be your target customer. Your pre-mortem pals are chosen because they have candor (which means that if it stinks, they’ll tell you… to your face… with no hesitation.) This group isn’t hyper-critical necessarily. They want to see you succeed, so they won’t inflate your hope with false niceties to avoid hurting your feelings.

If a person will tell you that your shirt is ugly, sign them up for your pre-mortem crew.

Executing a pre-mortem can be an informal process, however it is possible to ruin the validity of the pre-mortem. Be cautious to not “lead your witness” by building a worldview where your prototype is the only solution. You are best off not even telling them what your solution is or how it works. It is natural for us to go into pitch mode when we have someone looking at our prototype, but you wont be at the point of sale for your product every time. They will have to use your product by themselves, and “get it”.

Pre-mortems allow you to test your prototype, without any guiding, to see if it stands up on its own. A pre-mortem is like the first few shaky steps of a gangly giraffe; it looks like it will topple at any moment and you want to run over and prop it up, but you shouldn’t interfere if you want it to be running across the savannah someday.

To avoid the “let me just show you how this amazing product works” scenario, I’ve crafted a guide for you. This guide can be used whether you are “pre-morteming” by yourself, or with your group (the ones who are ok saying they don’t like your haircut).

THE GUIDE

  1. Refer to your customer profile so that you or your group can get in the customer’s mindset. Make sure to explain the pain points you identified for the primary persona.
  2. Let your pre-mortem pals interact with your prototype while you sit silently.
  3. Observe and document how they interact.
    • If you are doing this step virtually, have them write down or say everything that comes to mind including “Ok now I am clicking this button because it looks like it needs to be clicked… and now I am going to do this other thing”.
  4. Pretend to be in the future and your prototype has just failed in its most recent test.
    • NO REASON FOR FAILURE IS TO BE GIVEN YET.
  5. Have everyone participating in the pre-mortem write down how your prototype failed. Aim for lists with multiple failure options.
  6. Share and evaluate the responses. If you are doing this in a group, one person may see the prototype failing one way, and that may spark discussion on other ways no one had thought of.
    • I will warn you that this is a tough conversation to be a part of. However, you must encourage the dialogue. “This is great! Tell me more about how my prototype will fall on it’s face during the test!”
  7. Take your list of possible failures and start thinking of ways you can pivot.
    • Take no action now, unless a failure is eminent and will ruin the test. If that’s the case, you have to fix that! Otherwise, the list of failures is not guaranteed. Keep in mind that your pre-mortem pals may not be representative of your testing group.

If you are pre-morteming by yourself, you can skip steps 2 and 3. You should probably also skip any of the open discussion parts unless you want to talk to yourself out loud. And that’s totally fine if you do.

I enjoy pre-mortems. They teach you in so many ways. They serve as mini tests before your real test. They open up your eyes so that you can see your prototype from the customer’s point of view. They help you identify ways your prototype will stumble during the test. They let you plan pivots ahead of time, that you can act on later if your prototype does actually fail. I don’t dread testing prototypes because I know if it fails, I have a plan or two ready to go.

I challenge you to be vulnerable and find some folks who will look at your prototype with a critical eye. Plan for failure now instead of later.

*You may or may not know a Steve but I assure you that the names have been made up and any likeness to someone you know is purely coincidental.

2