Corvus Consulting

This post kicks off an idea I’ve wanted to start writing about for awhile, but never found the right way to without a long post with a bunch of examples. It seems more appropriate to offer examples of the idea as I find them, and to let the tags tie the posts together. So, welcome to the debut of Outputs vs. Outcomes.

Wha? Outputs vs. Outcomes?

I often notice in applications an emphasis on surfacing the relatively raw outputs of various data aggregations. How many comments, followers, votes, signups, views, clicks, stars are questions commonly answered by social apps, and people using the application are expected to derive what they can from that.

But for my time, raw numbers leave application experiences stale and one-dimensional, defaulting to what computers prefer to offer rather than what works for non-calculator type people.

Where products really succeed, you’ll find a focus on creating great outcomes. That’s done by hooking up creative transformation of outputs (the raw numbers) into something that supports the needs and goals of the people using the software.

The examples in the ongoing Outputs vs. Outcomes series illustrate the difference better than my words can, and for each example I’ll declare it a win for Output or Outcome. Use the eponymous tag to find all posts on this theme, and call me out wherever you think I’m not being fair.

Kinzin’s Monthly Photos by Mail: Outcome Wins

Via Megan, I learned about a really cool service added to Vancouver-developed Kinzin: your top 10 photos are automatically printed and mailed out to people who prefer physical prints for just under $4 (to Canada; $3 in the US) by monthly subscription.

I haven’t gone through the execution yet, but it’s an instant win for Outcomes as a product concept: a low monthly fee lets you generate happiness out of your online activity for someone who can’t use the web. This passes the Kathy Sierra ‘Make your users rock’ test with flying colours. Congratulations to the Kinzin team.

Information architecture is more art than science. It requires the insight and sensitivity to detail of an artist, and the skill of a technician to understand what’s possible and how to make it all clear. That’s the job of information architecture – to understand various perspectives and to satisfy all of them.

Designing and documenting information architectures is a natural fit for me. Since starting out in technical writing a decade ago, I’ve been involved in some way with connecting human and business goals with the technical capabilities on hand.

I develop information architectures of various depths for content-driven websites, web applications for business and consumer markets, desktop applications and application add-ons . I strive to match my deliverables to the need of the product, the schedule and team culture, and provide a balance of visual and text-based descriptions of the product character and features.

Types of deliverables I provide:

Textual use cases with and without flowcharts

Concept and feature maps

User interface wireframes

Recommendation Reports

If you’re interested in the benefits of information architecture for your project, contact me and we can talk about it.

When developing information architectures and product, the first question is ‘who is this for?’ That question is also the beginning of good product managment, because it’s the beginning of understanding the people you build for.

My product management experience is primarily in the domain of web applications. I thrive on being able build bridges between users and the development teams, translating and advocating for stakeholders every step of the way. I complement my ability to make complex ideas clear by connecting personally with the user community. The result of this dialog is greater than any internal team can dream up, as it is shaped by the customers as much as the vendor’s goals.

My philosophy is that no product is an island. I favor co-opitition, where the strengths and weaknesses of products in the same space can be combined and offset through smart and open partnerships. The web is a new, exciting and dynamic space, but some simple rules still apply: be friendly, listen well, give people what they like.

To discuss product management needs for your startup or new product, contact me and we’ll talk.

In the few years I’ve been working as a consultant, I’ve seen a huge jump in the number of software teams that have some kind of specification process and documented requirements as part of their project. Just a few years ago, too many projects were created with no more than whiteboards, individual notes and emails to make clear what the software would do.

I’d like to say I was a major force behind that trend, but really, it’s just an idea whose time has come. Though many managers know that a good specification, tailored to fit the project schedule and budget, it can be impractical to have a dedicated analyst on hand through the whole project. As a spec writer, I can integrate quickly with teams and existing schedules, and bring sharper, shared definition to any project phase.

My experience creating actionable and easy to understand product specifications covers business applications for the desktop, the web and handheld devices, as well as online community websites, application plugins and more.

My product spec deliverables can include

Detailed text use cases with and without flowcharts

Feature design and functional requirements

User interaction storyboards

Product charters and overviews

Requirements improvement reports

To discuss the kind of product spec your project needs, get in touch and we’ll talk.