I'm a mild-mannered software consultant. My day job consists of guidance, architecture, coding, automated unit testing, coffee consumption: All the fun stuff I love about software development. As if that didn't consume enough of my precious little time on earth, I have this hobby, a thing called photography. Over the past several years, it's evolved into a passion, then an obsession, and finally the potential for some fun side-work.
Up until now, I was content shooting my kids' sporting events (the baseball/soccer/volleyball parents do their share to cover my web hosting costs). Over the past two years, I [unofficially] shot two weddings (my biased opinion is that I out-shot the paid pro, but opinions are like...). Today was a big deal: an opportunity to score a real wedding shoot. Ok, maybe not "score," but at least deliver a compelling proposal.
As we're preparing our proposal, my co-photog and I found out (just a few short hours before our meeting) that the bride wants the "digital negatives." In the photography business, giving away negatives (whether film or digital) is typically taboo: once you give away the original source to an image, the new owner may cut the photog totally out of the loop. This impacts potential revenue as well as control of the photo's usage. So our knee-jerk reaction was something like No Way! But... we figured we could offer up at least some type of compromise: maybe charge a bunch for the digital files, or even agree to handing over a subset of the images but skip the book-layout tasks, saving a ton of labor.
So on we went to meet the bride and groom today, as well as the groom's dad. With a bit of trepidation.
As the bride flipped through our sample images and books, she kept revealing more and more of what she liked, didn't like, loved... along with some hidden gems: how she likes the casual, candid shots over formal stuff, how there are some family squabbles between specific people that shouldn't be photographed together...
Most importantly, we found out why she wanted the digital images: for email, desktop background, screensaver, and her digital photo frame. In fact, she despises the chore of printing photos. And until she saw our sample albums, she didn't even want to purchase any prints (now she's totally jazzed about it).
The moment we realized this, we were able to turn this into something positve: we scrawled it right on the contract: Free web-ready and desktop-ready digital images with every print ordered. The bride was happy. The groom was happy. The dad was happy. And the photog's? Score! The icing on the cake? They admitted that no other photographers interviewed would even consider parting with digital copies. Double-score!
So... time to circle back, and somehow relate this to software consulting. Between the original customer requirements (a phone call the likes of "Hey David - these folks want us to shoot their wedding!"), and initial statement of work, a new requirement popped up at the last minute. A poorly-defined requirement at that: a simple one-liner with no context. But that one-liner triggered an almost-catastrophic set of potential responses:
- No way! (definitely would have killed the proposal)
- Sure, but you're gonna pay through the nose! (good chance that would have killed the proposal)
- You must not know anything about the photography business! (nice way to insult the customer's intelligence, and kill the proposal)
Do any of those responses sound similar to something you might have considered blurting out at some point in your past? C'mon, be honest...
Ok, so we avoided reacting, and instead simply mentioned this new requirement and asked her to give us a bit more information about the need for digital copies. And that's when the "why" behind the "what" surfaced. A very simple, sensible requirement. One that we could painlessly provide a solution for, as it had little impact on our workload and no significant risk to the contract's cost structure or the project itself.
In the end, we were able to deliver a proposal that directly met the customer's needs, simply because we asked questions and listened.
After all this rambling, I guess I'm just trying to remind myself (and others, if they've gotten this far) that listening and asking questions is such an important part of the requirements process. And, after reading the body language of the client, I realize it goes much deeper than that. By being able to ask the right questions, listen to the nuances and details of the responses, and then propose a sensible solution tailored for the customer, I believe this is where true business relationships are formed, and trust is established.
Were you listening???