• Skip to main content
  • Skip to primary sidebar

Teague Hopkins

Mindful Product Management

  • Home
  • About
  • Blog
  • Contact

Technology

Jan 06 2014

One Simple Trick for User Centered Design

How often has your company run a focus group or usability test and generated big fat report that just sits on the shelf somewhere full of great ideas the never get implemented?

You can do all the research you need, but if you don’t use it in your decision-making process, you’d be better off not having done that all.

In order for that data in the report to get used, it must be highly visible and personally relatable. We all know what happens when the team has to seek out the results and can’t see how they relate to their work.

Enter the Information Radiator

[box type=”info” style=”rounded” border=”full”]An information radiator is a large, highly visible display used by software development teams to track progress.[/box]
Photo Credit: hugovk cc
Photo Credit: hugovk cc

One of the best approaches I’ve ever seen to achieving salience like this is a variant on the information radiators used for things like bugs fixed, bugs reported, or server uptime.

After conducting a series of recorded usability session with end users, one particularly clever usability expert I know convinced the team to let him put data from the sessions on the information radiators in the office (in this case, large monitors). Rather than reduce the users to a set of charts, he compiled the recordings of each session, edited them down to the biggest pain points, and played this highlight reel of ‘users having difficulty’ in a loop on the big screens around the office.

Every time people came in the office, they saw the endless loop of users trying and failing to use the website. Having those results staring at them every day was a great way to motivate the team to fix the confusing spots, empathize with the user, and raise the salience of usability problems to a level normally reserved for technical errors.

Written by Teague Hopkins · Categorized: Main · Tagged: Evaluation, Evaluation methods, Human–computer interaction, Salience, Science, Software testing, Technology, Tests, Usability, User

Sep 12 2013

Lean Startup Panel Discussion

Last night I had the privilege of moderating a panel discussion with four other lean startup practitioners at the Ballston BID Launchpad in Arlington, VA. The event was organized by Lean Startup Machine, and the five of us will all be mentoring at the upcoming Lean Startup Machine DC on September 20-22.

Moderator

Teague Hopkins – Founder of THG, Lean Startup Coach. THG helps teams at corporations, nonprofits, universities, and government agencies innovate more efficiently and effectively.

Panelists

Frank DiMeo – VP, Technical Staff at In-Q-Tel. In-Q-Tel is a not-for-profit venture capital firm that invests in high-tech companies to help the CIA and other intelligence firms equipped with the latest in information technology in support of United States intelligence capability.

Frank Taylor – CEO of Restin, Head of Partnerships at Fosterly. Restin provides robotic massage chairs for rent and lease to the engagement marketing industry and for various applications in the corporate wellness & hospitality space. Fosterly is a platform to organize and share entrepreneurial knowledge.

Bruce Mancinelli – Executive Director, Incspire. Incspire is a business incubator education program that supports emerging businesses and startups through the pairing of mentor teams to each incubated company in the program.

Laura Kennedy – Head of Corporate Development, Living Social. Living social  is a deal-of-the-day company that features discounted gift certificates usable at local or national companies. Based in Washington, D.C.

Panel Recording

Topics

  • What was your first introduction to Lean Startup?
  • An introduction to the components of Lean Startup Methodology.
  • How have you implemented the lean startup methodology at your company?
  • What’s the most surprising thing you’ve learned from running an experiment?
  • We’ve all heard about skunkworks. The goal is to insulate innovation teams from the culture and oversight of the larger organization. To be successful, do companies need to separate those doing innovation from those running operations?
  • What will we learn at Lean Startup Machine?
  • What are some tips for getting the most out of Lean Startup Machine?

Written by Teague Hopkins · Categorized: Main · Tagged: Business, Culture, Lean, Lean Startup, Marketing, Technology

Feb 22 2013

Interview with Elliot Susel: Tech Risk + Agile

An interview with Agile expert Elliot Susel about using agile to mitigate tech risk.

Full Transcript

Teague Hopkins: Welcome. I’m Teague Hopkins. Today I’m here with Elliot Susel, the senior project manager and primary Agile evangelist for Taxi Magic, an app that helps people book ground transportation. Elliot’s an expert on Agile has worked on it for five years at Accenture and now you’re at Taxi Magic. Is that right?

Elliot Susel: That’s right.

Teague: To start off, what is Agile for people who are not familiar with it?

Elliot: The core idea behind Agile is a series of practices that help you to develop software iteratively. That’s the core idea behind the Agile methodology.

Teague: For some of our entrepreneur listeners, how can Agile help ameliorate tech risk, this idea that we’ve talked about as the challenge of whether we can actually build the things that we’re trying to build?

Elliot: As you’re working toward a technical solution there’s a number of tools from the Agile methodology that you can use to help you work iteratively and to work your way toward a solution rather than having some grand vision and being unable to test that vision until you’ve got this final product and it may fall on its face. The idea is that by having value that you can deliver incrementally by using Agile processes and working iteratively you can test your assumptions as you move along and then also refine your ideas. As it relates to technology specifically, there’s a couple things that you can start to accelerate by working iteratively. The first is that not only are you able to improve the product, you’re also able to improve the team that’s working on the product. So, one of the core Agile practices is this idea of a retrospective where the team talks about what’s going well, what’s not going well, and specific actions that we can do to improve in the future.

Teague: I know that you’ve got a couple of retrospectives that you use on a regular basis. Can you explain what your favorite one is and how it works?

Elliot: Yeah. One of the favorite retrospectives that I’ve ever done was oriented towards gaming and I said, we can make this retrospective not just an exercise where we make some columns on a whiteboard and say here’s what we liked, and here’s what we didn’t like, but we could get really creative. So, we turned it into this game where you would draw on the whiteboard anything that would accelerate us, and you would draw on the whiteboard anything that would impede us, and we were represented as a ship in the ocean. We ended up with giant squid, and fire-breathing monsters, and anchors, and airplanes, and sails, and party cakes, and all kinds of representations, and

Teague: And that still helped you get towards the goal you were getting at?

Elliot: Each one was not just a fun thing to draw, but also had with it an association. I think that the giant squid had to do with our testing, and the team then had to figure out well how do we solve this issue of testing and then they also drew something in to deal with the giant squid which was a fun exercise.

Teague: Great.

Elliot: It kept it light-hearted and it got everyone really engaged.

Teague: Uh huh. (affirmative) It sounds like a lot of this idea of working on the technology in an iterative way sort of dovetails with a lot of the Lean startup methodologies. In your experience have you seen any byplay there?

Elliot: I would say yes and no. You can do Agile without being Lean, which is unfortunate, but I would say that there’s really three roles on an Agile team. One role is the product person, the product owner more formally, where their vision and their goal is to set the vision for the team and define what the team should be building. Now a product owner may or may not be working according to Lean principles and can march the team in a direction that may or may not be consistent with Lean. There’s the scrum master whose job it is to remove impediments and to help the team move as quickly as possible.

Teague: Uh huh. (affirmative)

Elliot: And, the team whose job is ultimately to be in the iteration.

Teague: Uh huh. (affirmative)

Elliot: And the more time they spend in the iteration and not on distractions, the better.

Teague: If you were talking to somebody who’s adopting Agile for the first time or trying to adopt Agile for the first time, what would be the most important piece of advice you can give them in terms of taking their first steps?

Elliot: Find a really good coach. Find the best possible practitioner that you can actually spend time with. And, to use the words of the scrum master and practitioner that I learned from, to spend time in their dojo.

Teague: Uh huh. (affirmative)

Elliot: A scrum master really is creating an environment and it’s not just this series of practices; although the practices are important, but it’s an organizational mindset where yes the team can build incrementally and that’s lovely and that mitigates your tech risk. But, also, it helps if the product team is also thinking incrementally and how can we test our assumptions incrementally, and how can we incrementally work toward our solution in the best possible way?

Teague: Excellent. Well, thanks, Elliot, for joining us today. You can find out more about Agile, and Elliot, and Taxi Magic at Elliot’s website at www.elliotsusel.com. Thanks for listening.

This interview originally appeared in The Three Biggest Risks to Your Startup.

Written by Teague Hopkins · Categorized: Main · Tagged: Agile, Agile software development, Business, Lean, Lean Startup, Management, Project management, Risk, Scrum, Software development, Software development process, Software engineering, Software project management, Technology

Oct 23 2012

A Better Website in One Afternoon

Photo by vincen-t on Flickr

There’s a simple experiment you can run in a single afternoon that will give you all the information you need to improve the website for your restaurant or bar. Most bar and restaurant websites are terrible. This is almost a mantra in the web design community. Running a great restaurant doesn’t require having the skills to create a great website, but a good website also doesn’t require hiring an expensive firm to design and build your site. Visual designs are time-consuming and often need some technical knowledge to carry out but you can create a perfectly acceptable visual design based on a customizable template. A great website might take expertise, but it only takes a little to take a bad website and make it good enough.

The biggest gain (and best way to set yourself apart) is not how your site looks, but how it makes the user feel. User experience (UX) matters and it’s not hard to be just a little better than your competition.

The Simple UX Experiment

  1. Recruit 5 potential customers from your local Craigslist board (offer cash or a discount or voucher for a meal at your restaurant).
  2. [box type=”tick”] Example
    Come spend 10 minutes helping us test our Thai restaurant’s website. We’ll give you a voucher for $20 off a meal to use whenever you like. Respond by email with your availability and we’ll let you know where to show up.[/box] [box type=”alert”]Don’t reveal the name of your restaurant. You don’t want people to become familiar with your website until you can watch the process.[/box]
  3. Stagger arrival times by 15 minutes to give yourself time to reset between test subjects. When your first volunteer arrives, sit them down in front of a computer and tell them the name of your restaurant. See if they can find your website on the first try. [box type=”tick”]Explain to your volunteer that you’d like them to speak their process out loud, stream of consciousness style, so that you can understand where they hit problem spots.[/box]
  4. Ask them to try to find your restaurant’s address on the website. See how much time and how many clicks it takes. Pay attention to how long they spend deciding which links to click, and see if they make mistakes or get frustrated.
  5. Ask them to find a menu on your site. See if they can find and open the menu. See if they get confused or lost if they are downloading a PDF.
  6. Ask them to make a reservation. See if they use an online reservation service (if you have one) or if they find a phone number to call.
  7. BONUS: Ask them to try each of these tasks on a smart phone or other mobile device.

Going through this process with 5 volunteers will take you less than 2 hours and only $100 (or less if you’ve offered vouchers). The insights gained from actually watching your customers struggle with your website will uncover the most common barriers that are keeping visitors to your website from becoming visitors to your restaurant. As an added benefit, even customers who succeeded at using the old website will be happier with the improved user experience. A few simple changes can make a big difference.

Written by Teague Hopkins · Categorized: Main · Tagged: Customer, Experiment, Technology, User

Aug 29 2012

Good Enough Technology

Most people don’t need the cutting edge. If you do audio production, you might need top-of-the-line monitor speakers or pro headphones, but most people are content with the earbuds that come with their iPods. If you make your living trading stocks in real time, you might need a blazing-fast and redundant internet connection, but most people are perfectly happy with their garden-variety DSL or cable internet connections. If your business is large-format photo printing, you probably need to invest in the best printers you can afford, but for most people, a standard inkjet or laser printer is all they need.

What You Really Need

So what do you need for those activities that are not part of your core? If your business is feeding the homeless or providing a safe space for victims of domestic abuse, you still have office needs. You still need to coordinate your team and file your paperwork. You could invest in high-powered ultraportable notebooks, a dedicated server, and a fat data pipe. In fact, some technology consultants will tell you that these investments will pay for themselves in increased productivity. They may, but that doesn’t mean they are the best investment for your organization.

Pareto principle

Photo by Mary-Kay G

The Pareto Principle, named for Vilfredo Pareto, and nicknamed the 80-20 Rule, states that roughly 80% of the effects come from 20% of the causes. 80% of your profits come from 20% of your customers; 80% of the world’s income is controlled by 20% of the world’s population; 80% of healthcare resources in the USA are consumed by 20% of the patients.

How to Leverage Pareto

If the Pareto principle holds true for technology spending (and in my experience, it is close enough to be a good estimate), it follows that your organization can have 80% of the existing cutting-edge technical capacity for 20% of the potential cost. Cloud hosting services, Google apps for business, and internet connections that are fast enough for almost all organizations can all represent significant savings for you and help focus on using your resources to serve the organization’s mission.

What will you do with the 80% of the cost that you have saved? If technology is not core to your business there is probably a much more powerful point of leverage for that investment. Get your good-enough technology, and put the rest of your investment towards your organization’s core mission.

Written by Teague Hopkins · Categorized: Main · Tagged: Business, Customer, Pareto principle, Productivity, Technology, Vilfredo Pareto

  • Go to page 1
  • Go to page 2
  • Go to Next Page »

Primary Sidebar

Copyright © 2023 Teague Hopkins
 

Loading Comments...