Why use cases should drive technology design

During a briefing from Microsoft's xRM team, the question of how to integrate structured and unstructured data arose. If xRM (the Dynamics platform) is good at the structured stuff, and SharePoint is good at unstructured content, what's the right way to bridge the two?

Back in my Oracle days, we faced exactly the same question. At a technology level, there's no obvious answer. Bring together two development teams (the structured and unstructured specialists), and you'll first get a lot of technical-level discussions. How should security work? What API changes might be needed? How will metadata span the two kinds of information?

Unfortunately, there's no immediately obvious answer to these questions. In fact, the options are so broad, and the risk of technological quagmires so great, that the endeavor might easily grind to a halt. People ponder the options, argue over which one is best, go back and ponder some more...

At Microsoft, a clear use case accelerated this discussion. The Public Sector group developed a constituent services application for local governments that combines both SharePoint and xRM. Notice how specific the application, the Citizen Service Platform, is. Not all government, but local government. Not several government functions, but constituent services. 

Undoubtedly, the Citizen Service Platform team made it clear which kinds of integrations were important, and which weren't. It's not too hard to generalize the use case to other situations. After all, we're talking about the same CRM platform that property managers and church pastors use, for different but similar purposes.

For people who are already sold on use cases as the right foundation for designing products, this might seem like a "Well, duh!" sort of observation. However, many product teams go full speed ahead with only the haziest use case, or to be honest, none at all. If their product decision-making process is too slow, or too error-prone, they might reconsider the value of a very specific use case.

[Cross-posted at The Heretech.]


re: Why use cases should drive technology design

I'd agree that use cases should drive product design, but sayin they should drive technology is another matter. Products are the means of commercializing a technology, but a product as the embodiment of a technology does not mean that they are the same thing.There is no reason to worry about the ease of use of a technology. Focus research instead on doing something that has never been done before. Leave the produtizations to others. The value of such products is in the effort required to make it acceptable to the market. Some markets might need simple, but they are in the late market, so a technology might undergo several productizations working towards one simple enough to succeed in the late market.

re: Why use cases should drive technology design

I'm so with you on the idea of driving a product by use cases!Please check out this post about SSNiF Scenarios, as a refinement to use cases.SSNiFs are a way of connecting the Stakeholder (often customer/persona) to the Situations they are in to the resulting Need, to the potential Feature that resolves the need.http://bit.ly/ItBXsBest regards,Philip HaineProductVision.org@dphaine

re: Why use cases should drive technology design

Hi,· We have just added your latest post "Why use cases should drive technology design" to our http://www.projectgrant.info. You can check the inclusion of the post, Visit ”http://www.projectgrant.info/story.php?title=why-use-cases-should-drive-technology-design” We are delighted to invite you to submit all your future posts to the directory for getting a huge base of visitors to your website and gaining a valuable backlink to your site.Warm RegardsProject Grant Teamhttp://www.projectgrant.info

re: Why use cases should drive technology design

This is a great information. I would love to have one of this. By the way,i have found a link that everyone can also check on your blog and you can publish your news for free, such as this article you have. Im actually fund of reading blogs and articles and i think you should check it out. http://www.freepressreleasecenter.com/