- T-SQL Tuesday #002: A Puzzling Situation
- T-SQL Tuesday #003: Relationships
- T-SQL Tuesday #004: IO
- T-SQL Tuesday #005- Reporting
- T-SQL Tuesday #006: “What About BLOB?”
- T-SQL Tuesday #007: Summertime in the SQL
- T-SQL Tuesday #008: Gettin’ Schooled
- T-SQL Tuesday #009: Beach Time
- T-SQL Tuesday #010 – Indexes
- T-SQL Tuesday #011: Misconceptions
- T-SQL Tuesday #012 – Why are DBA skills necessary?
- T-SQL Tuesday #013 – What the Business Says is Not What the Business Wants (Summary)
- T-SQL Tuesday #014 – Resolutions (summary)
I was giving a presentation recently and someone in the audience started to ask about why I recommended against a certain technique. Without getting into it, this person kept saying that she had to implement things her way since the “business” said they needed it done that way. However a little digging showed that the business didn’t really understand the technology. They were asking for a result, and she took them literally in how she implemented a process. A classic impedance mismatch.
I think we’ve all had situations that are similar. The business, the client, the customer, is asking for something, but they don’t know how to ask those of us building the technology. Or they don’t understand the implications of asking for something like “absolutely zero data loss” to be implemented.
The official topic this month is:
What issues have you had in interacting with the business to get your job done.