Separating Problems From Software In Technology Based Conversations

576 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
576
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Separating Problems From Software In Technology Based Conversations

  1. 1. Separating Problems from Software in Technology-Based Conversations<br />Peter Ellis, MSIM<br />InfoCamp Seattle<br />October 10, 2009<br />
  2. 2. On Twitter? Please do live tweet. Tag with #infocamp! React!<br />Twitter: peterellis | me@petercellis.com | Peter Ellis, MSIM<br />
  3. 3. You’re talking about a problem with the company’s ability to locate documents. The company, as a Microsoft shop, has at its disposal a license for Microsoft SharePoint 2007 Enterprise Edition. You begin to discuss how the problem might be solved with SharePoint, since this will reduce the IT department’s grumblings about the plan and they were planning on installing it anyway.<br />Twitter: peterellis | me@petercellis.com | Peter Ellis, MSIM<br />
  4. 4. What’s the problem?<br />Twitter: peterellis | me@petercellis.com | Peter Ellis, MSIM<br />
  5. 5. Why bother separating the two?<br /><ul><li>Clarity of definitions
  6. 6. Ability to ensure that you actually solve the problem
  7. 7. Need to be able to define scope
  8. 8. Sanity</li></ul>Twitter: peterellis | me@petercellis.com | Peter Ellis, MSIM<br />
  9. 9. “We needtoshoveitoutthedoornow!”<br />Great, but.. Really? You sure about that? Is it defined?<br />Is it scoped? Does pushing it out damage our reputation?<br />Twitter: peterellis | me@petercellis.com | Peter Ellis, MSIM<br />
  10. 10. Technology is a medium. If you don’t know the problem, if you don’t define scope….<br />Twitter: peterellis | me@petercellis.com | Peter Ellis, MSIM<br />
  11. 11. …how do you know what technology you need?<br />Twitter: peterellis | me@petercellis.com | Peter Ellis, MSIM<br />
  12. 12. OR<br />Twitter: peterellis | me@petercellis.com | Peter Ellis, MSIM<br />
  13. 13. So how do you do this?<br /><ul><li>Look at the long-term impact
  14. 14. Dialog about the specific problem being attacked. Ask why.
  15. 15. Ask questions intended to attack the problem
  16. 16. Thinking about the technology is not bad, it’s distracting at the wrong times</li></ul>Twitter: peterellis | me@petercellis.com | Peter Ellis, MSIM<br />
  17. 17. THERE IS NO ONE SIZE FITS ALL<br />THERE IS NO ONE SIZE FITS ALL<br />THERE IS NO ONE SIZE FITS ALL<br />THERE IS NO ONE SIZE FITS ALL<br />THERE IS NO ONE SIZE FITS ALL<br />THERE IS NO ONE SIZE FITS ALL<br />THERE IS NO ONE SIZE FITS ALL<br />THERE IS NO ONE SIZE FITS ALL<br />Twitter: peterellis | me@petercellis.com | Peter Ellis, MSIM<br />
  18. 18. Now it’s your turn. Let’s talk.<br />Twitter: peterellis | me@petercellis.com | Peter Ellis, MSIM<br />

×