Tag Archives: requirements

The Importance of Perspective

Steve Johnson has a video on his site that shows a wonderful optical illusion. I’ve embedded it here for your viewing convenience.

This video is a great example of how important a role perspective plays in how we interpret our environment.

Perspective is also incredibly important for people when researching, designing or building products.

Specifically for Product Managers, it’s important to be conscious of how your perspective (your background knowledge, assumptions and existing viewpoints) on a situation influences how you interpret it.

To maximize your perspective, and avoid false assumptions and conclusions, try to get as many inputs as you can when researching requirements. This does not simply mean talk to more people, but make a conscious effort to to improve your domain knowledge, document and validate your assumptions clearly, and talk to different types of people in different roles, in different types of companies and with different needs.

It’s actually quite amazing how much insight you can gain by consciously broadening your perspectives on a given situation.

Saeed

Product Management in Pictures #5: If Hardware was built like Software

Good Resilience vs Bad Resilience

Pretty much everyone agrees that resilience is good, especially in software. When one of a million external dependencies fails you don’t want your software falling over like a poorly designed tower.

So how could resilience possibly be bad? Resilience goes bad when an application gracefully – and silently – handles an error even though the error was really, really bad. (One of these examples came up at work today but I won’t say which one). And apologies to Jeff Lash.

Good Resilience: Your application is flexible enough to let users install it on machines that don’t exactly meet the minimum resource requirements. After all, let’s not be picky.

Bad Resilience: Your application is willing to let users install it on a machine that will run so poorly that it will make the application look bad. Users might say “Does it really need two gigabytes of memory? Really?” but if the application is using some sort of SQL-based database storage, yeah, it probably does. And when it runs like a dog? It’s your company’s fault.

Good Resilience: Your application doesn’t scream and crash when a file it expects to find isn’t present. Yay for not crashing.

Bad Resilience: When an expected file is missing, your application merrily continues along and provides the user with the wrong results. Like the previous example, the application is a bit too resilient.

Good Resilience: The application lets any user run it.

Bad Resilience: The application doesn’t check to see if the user has sufficient privilege to carry out the operation and indicates that something is missing when, in fact, it’s only missing because the user can’t access it. Windows apps may not care about this much, but for those “UNIX-Enterprise” apps, this can be a real headache.

Most of the time requirements capture what happens when all the stars align and everything works correctly. But spend some time with your pre- or post-sales field staff and it quickly becomes apparent that requirements also have to describe what should happen in bad situations that can be reliably predicted (or, more realistically, how the next version should handle the situations that have the field people pulling their hair out).