4. What you DON’T need -
• A technical background
• An ability to write code
• A knowledge of every possible technology that
could be used
5. What you DO need -
• An ability to clearly describe what you want
something to DO
6. Start with a workflow
• Think through & describe the steps of how
something should work
7. Then draw up your requirements
• Make a list of what you need the technology
to do
• Note any specific standards the technology
will need
• Note any systems or other technologies the
new technology needs to interact with
• Any other important things it needs to do
8. Let everyone do what they do best
• You know best what you want to be able to do
with a tool
• Let the developer(s) sort out exactly how this
is done – that is not your problem
9. Talk The Same Language
• Be very clear about what you both mean.
10. Be Flexible
• You don’t have to understand all the technical
details, you just need to be able to understand
how something might impact on your
workflows to make a decision.
• Keep talking- it’s about teamwork.
11. The Hardest Things Of All
• It’s your call in the eternal time versus
perfection battle
• Let the developers get on with it – trust their
expertise
12. And don’t forget…
• Development teams need regular supplies of
kittens, coffee, cake & beer
Thankyou!