Discussion on:

12
Comments

Join the conversation!

Follow via:
RSS
Email Alert
4 Votes
+ -
Aaargh!
Tocsin 29th Feb 2012
Come on - "technical resources" - how about calling us "people" ?
0 Votes
+ -
Aaargh! x 2
PMPsicle 5th Mar 2012
A QA person doing testing????? Sorry that's a QC function.

QC = Quality Control = Testing
QA = Quality Design of Processes = Business Process Management = Identify where you need to test & what you need to do to ensure quality is built in.
0 Votes
+ -
Moderator
QED
4 Votes
+ -
He's writing in "business-ese", so that business managers can understand him. wink
1 Vote
+ -
Great Article
blarman 29th Feb 2012
Even for non-technical managers, #10 is important. Your best ideas will always come from the people closest to the source of the problem because they have to deal with it every day. Your business will improve much faster if you listen to them and it is a great way to build rapport.
Lehnerus2000 has it right --- I am using the language of business, or at least trying to. I've been a technical resource for most of my life and don't have any problem with that terminology. Still, it may make sense to start drafting "Ten Things that Technical Resources Have in Common with People" for use by business managers.
0 Votes
+ -
Relationships
zrojasr@... 29th Feb 2012
These are questions that naturally occur when a healthy relationship has developed between IT and the business community. And like all relationships it takes the right people in an open environment willing to build trust and maintain an honest dialogue.
0 Votes
+ -
Nice article. I agree. I always ask IT developers the question "show me the evidence that ....", it works, people want this, data is well managed etc, etc.

Such a simple question always exposes the issues.
'Show me the evidence'... great mantra for getting to the truth behind the curtain.
It???s also worth considering, and also prudent, though not always popular, to ask the current team(s) to help plan the demigration of this ???new thing.??? In five to ten years, someone else is going to have to handle that task, and the understanding of this ???new thing??? may be thin or hard to find at that time. If you can engage the current skillset to help plan the ???sun setting??? of this ???new thing???, it helps the next team and encourages a business success. You can also help this ???new thing??? have a good reputation at sun setting time, because it will be more favorably acknowledged by the next team. Think about what resources your current team would have appreciated from the team prior to them.
I think the way you are thinking really separates your attitude from the often-heard approach of "I certainly won't be around in X years when this stops working".
Keyboard Shortcuts:
Prev
Next
Toggle
Join the conversation
Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]

Join the TechRepublic Community and join the conversation! Signing-up is free and quick, Do it now, we want to hear your opinion.