Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Effective Specification Writing

6,286 views

Published on

Workshop on Effective Specification writing.

Published in: Technology, Business
  • Thanks Reuben, it really dependents on how much of a straight-jacket you place on bidders, To me the answer is a specification has to include the minimum technical requirements, something about the minimum performance requirements (outputs), but largely a statement of the problem (outcomes) you are trying to solve with a challenge to suppliers as to how they propose to solve the problem. The more you focus on inputs as opposed to outcomes, the more you restrict innovation,
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Does specification restricts innovation, if yes, why ?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Effective Specification Writing

  1. 1. Effective specification writing Dr J Gordon Murray
  2. 2. Your challenge <ul><li>Find a partner </li></ul><ul><li>Find a space </li></ul><ul><li>Sit back-to-back with your partner </li></ul><ul><li>One partner (a) will be given a picture </li></ul><ul><li>Describe the picture you have been given to your partner (b) </li></ul><ul><li>Partner (b) produces description of what the partner (a) has told them </li></ul><ul><li>Do not share your results </li></ul>
  3. 10. Which one was being specified? A B C G D E F
  4. 11. What do you consider to be the purpose of a specification?
  5. 12. A specification is a document describing the buyer’s needs, which enables providers to propose an appropriately costed solution to meet those needs. In parallel it provides a means to tender evaluation.
  6. 13. Procurement Cycle 8. Closure / Review Need 1. Identify Need 2. Develop Business Case 3. Define Procurement Approach 4. Supplier Appraisal 5. Tender Evaluation 6. Award Contract 7. Manage Implementation of Contract
  7. 14. What do you consider to be the minimum requirements of an effective specification?
  8. 15. Minimum requirements of a specification <ul><li>Set out the buyer’s requirements </li></ul><ul><li>Provide a shared understanding of each party’s responsibilities </li></ul><ul><li>Reflect users views </li></ul><ul><li>Link to the evaluation criteria </li></ul><ul><li>Form the basis for future contract management </li></ul><ul><li>Fit with T&Cs </li></ul><ul><li>Be clear, complete, concise, consistent and in plain English </li></ul>
  9. 16. Why are specifications important?
  10. 17. Why specifications matter <ul><li>Mistakes may affect end users </li></ul><ul><li>Mistakes may undermine strategic aims </li></ul><ul><li>A critical contract management document </li></ul><ul><li>A critical legal document </li></ul><ul><li>Information omitted can lead to suppliers making wrong assumptions </li></ul><ul><li>Over-specifying leads to increased cost </li></ul><ul><li>Overly prescriptive restricts innovation </li></ul><ul><li>Media attention </li></ul>
  11. 18. A specification … <ul><li>Can encourage providers to focus on outcomes </li></ul><ul><li>Can encourages innovation which stating essential requirements </li></ul><ul><li>Provide a structure for delivery </li></ul><ul><ul><li>Timescale </li></ul></ul><ul><ul><li>Payments and incentives </li></ul></ul><ul><ul><li>Flexibility to test innovation </li></ul></ul><ul><ul><li>Performance measurement </li></ul></ul><ul><ul><li>Contract management activities </li></ul></ul><ul><li>Can improve organisation’s profile </li></ul>
  12. 19. EU principles <ul><li>Equal treatment </li></ul><ul><li>Non-discrimination </li></ul><ul><li>Transparency </li></ul><ul><li>Proportionality </li></ul><ul><li>Objectivity </li></ul>(Traffic Signs and Equipment Ltd and DPRD & DFI, High Court NI, WEA8075)
  13. 20. What would be a good specification writing process?
  14. 21. The specification process Define scope Identify info sources Gather info Agree Contract manager Decide Spec type Draft KPIs Draft Evaluation criteria Draft spec Reflect on consultation Amend spec Consult on draft QA Writing an effective specification requires good project management and time The market Current position Industry Stds. alts Respond to Clarification requests Despatch NB EU rules
  15. 22. Who should be involved in writing the specification?
  16. 23. The buying decision making unit <ul><li>Initiator who first suggests buying the product or service </li></ul><ul><li>Influencer whose comments affect the decision made </li></ul><ul><li>Decider who ultimately makes all or part of the buying decision </li></ul><ul><li>Buyer who physically makes the purchase </li></ul><ul><li>User who consumes the product or service </li></ul>(Wilson, Gilligan and Pearson, 1992)
  17. 24. Stakeholder Analysis Matrix Potential Strategies Assessment of Impact Stakeholder Interests Stakeholder
  18. 25. Pick a contract you are familiar with and conduct a stakeholder analysis
  19. 26. Stakeholder Analysis SUBJECTS Low power High interest +/- Management could encourage conditions to increase power of + ive and encourage to become Players or neutralise - ive Power Level of interest PLAYERS High power High interest +/- Significant stakeholders who deserve sustained management attention CROWD Low power Low Interest Potential rather than actual stakeholders Interest an/or power could be raised, but unlikely to be worth management time/effort CONTEXT SETTERS High power Low Interest Can influence overall future context Management should seek to raise awareness and develop + ive interest and convert to Players (Ackermann & Eden, 2011)
  20. 27. What could go wrong with a specification?
  21. 28. Managing risk <ul><li>Risk analysis </li></ul><ul><li>Risk assessment </li></ul><ul><li>Risk mitigation </li></ul>
  22. 29. Risk threat responses <ul><li>Reduction (treat) </li></ul><ul><li>Removal </li></ul><ul><li>Transfer </li></ul><ul><li>Retention </li></ul><ul><li>Share </li></ul>
  23. 30. Risk assessment Mitigation Proximity Impact Probability Risk
  24. 31. Thinking of your spool of thread, carry out a procurement risk assessment
  25. 32. Outcomes, outputs and inputs: what’s the difference?
  26. 33. Outcomes, outputs and inputs <ul><li>Outcomes say what you are aiming to achieve, but the achievement may be beyond the contract term </li></ul><ul><li>Outputs (Functional and Performance specifications) say what measurable services or activities providers must deliver to achieve outcome </li></ul><ul><li>Inputs (Technical or Conformance specifications) detail how to meet an outcome. </li></ul>
  27. 34. Using the thread example you worked on earlier: Define: outcome, output, input
  28. 35. What are the relative pros and cons of outcome, output and input specifications?
  29. 36. <ul><li>Where outcome based is not possible </li></ul><ul><li>Delivery of outcomes possibly reduced </li></ul><ul><li>Flexible to level of skills and knowledge </li></ul><ul><li>Address difficulties with purist approach </li></ul>Mix of above <ul><li>Repetitive supplies </li></ul><ul><li>Repeat of successful project </li></ul><ul><li>Technical requirements </li></ul><ul><li>Fails to deliver outcomes </li></ul><ul><li>Requires technical skills </li></ul><ul><li>Risk lies with client </li></ul><ul><li>Stifles innovation and VFM </li></ul><ul><li>Easier bid evaluations </li></ul><ul><li>Measurable success </li></ul><ul><li>Makes providers aware of non-negotiables </li></ul>Input <ul><li>Where outcome based is not possible </li></ul><ul><li>Fails to deliver outcomes </li></ul><ul><li>Proxies may be unsuitable </li></ul><ul><li>More risk lies with client </li></ul><ul><li>Stifles innovation and VFM </li></ul><ul><li>Quite easy to specify </li></ul><ul><li>Measurable success </li></ul><ul><li>Easier bid evaluations </li></ul>Output <ul><li>Whenever possible. Providers define the inputs and outputs to meet the specification </li></ul><ul><li>Difficult bid evaluations </li></ul><ul><li>Difficult to measure success </li></ul><ul><li>Depends on relationships </li></ul><ul><li>Scatter gun approach </li></ul><ul><li>Easy to specify </li></ul><ul><li>Direct link with outcomes </li></ul><ul><li>More risk with provider </li></ul><ul><li>Encourages innovation </li></ul>Outcome When to use Possible disadvantages Advantages
  30. 37. What’s the difference between a mandatory and desirable feature?
  31. 38. Evaluation criteria EU rules apply
  32. 39. Evaluation criteria: EU position <ul><li>Must be linked to the subject mater of the contract </li></ul><ul><li>MEAT or lowest price </li></ul><ul><li>Including: </li></ul><ul><ul><li>Quality </li></ul></ul><ul><ul><li>Price </li></ul></ul><ul><ul><li>Technical merit </li></ul></ul><ul><ul><li>Aesthetic and functional characteristics </li></ul></ul><ul><ul><li>Environmental characteristics </li></ul></ul><ul><ul><li>Running costs </li></ul></ul><ul><ul><li>Cost effectiveness </li></ul></ul><ul><ul><li>After sales service </li></ul></ul><ul><ul><li>Technical assistance </li></ul></ul><ul><ul><li>Delivery date and delivery period </li></ul></ul><ul><ul><li>Period of completion </li></ul></ul><ul><ul><li>… </li></ul></ul>
  33. 40. Using the thread example you worked on earlier: Draft performance measures and evaluation criteria
  34. 41. What should be in the specification?
  35. 42. Specification content <ul><li>Background and context </li></ul><ul><li>Current position and any anticipated changes </li></ul><ul><li>Scope </li></ul><ul><li>Required outcomes, and where necessary, proxy outcome indicators and non-negotiable outputs and inputs </li></ul><ul><li>Target groups </li></ul><ul><li>Geographical area covered </li></ul><ul><li>Volume required </li></ul><ul><li>Interfaces/dependencies </li></ul><ul><li>Delivery timescales and contract period </li></ul><ul><li>Payment terms and incentives </li></ul><ul><li>Key risks and who will be responsible for managing </li></ul><ul><li>Performance measures </li></ul><ul><li>Progress reporting </li></ul><ul><li>Policy through procurement issues </li></ul><ul><li>End of contract </li></ul><ul><li>Person to contact for clarification </li></ul>
  36. 43. Using the thread example you worked on earlier: Draft a specification
  37. 44. How can you ensuring the spec is fit for purpose?
  38. 45. Market sounding
  39. 46. Market sounding <ul><li>Presenting draft specification to the market can: </li></ul><ul><ul><li>Improve likelihood of receiving bids </li></ul></ul><ul><ul><li>Increase potential for competition </li></ul></ul><ul><ul><li>Avoid ‘brand’ specifying </li></ul></ul><ul><ul><li>Contribute to value analysis and value engineering </li></ul></ul><ul><ul><li>Demonstrate good will </li></ul></ul><ul><ul><li>Demonstrate transparency </li></ul></ul><ul><ul><li>Reduce costs </li></ul></ul><ul><ul><li>Assist with QA </li></ul></ul><ul><li>Heath warning: handle with care, risk manage </li></ul>
  40. 47. Pass your draft specification to a different team for QA
  41. 48. QA for specifications <ul><li>Is it clear: </li></ul><ul><ul><li>Who requires it? </li></ul></ul><ul><ul><li>What is required? </li></ul></ul><ul><ul><li>Why it is required? </li></ul></ul><ul><ul><li>Where it is required? </li></ul></ul><ul><ul><li>When it is required? </li></ul></ul><ul><ul><li>How it is required? </li></ul></ul><ul><li>Could anything have more than one interpretation? </li></ul><ul><li>Has plain English been used? </li></ul><ul><li>Is the information in the specification still current? </li></ul><ul><li>Does the specification fit with evaluation criteria? </li></ul><ul><li>Is it legal? </li></ul><ul><li>Does the specification conflict with T&Cs? </li></ul><ul><li>Has opportunity for fraud been minimised? </li></ul><ul><li>Are there suppliers who can delivery? </li></ul><ul><li>Is it skewed towards a small number of providers? </li></ul><ul><li>If everything asked for was provided, would we have what we are really looking for? </li></ul><ul><li>Is risk appropriately allocated? </li></ul><ul><li>Are H&S and equalities addressed? </li></ul><ul><li>Has any change to the budget been signed off? </li></ul><ul><li>Have stakeholders, particularly users, been prepared for any change the procurement may bring? </li></ul>
  42. 49. Recommended reading: CIPS Contract Management Guide by R.D. Elsey, 2007.
  43. 50. Effective specification writing Dr J Gordon Murray [email_address] www.Twitter.com/DrGordy www.slideshare.net/drgordonmurray
  44. 51. How can you use the specification to achieve cost reduction and policy through procurement objectives?
  45. 52. Outcome based specifications <ul><li>Detail the outcomes you want to achieve </li></ul><ul><li>Avoid saying how the outcomes are to be achieved </li></ul><ul><li>Encourage innovation </li></ul><ul><li>Help ensure you meet user needs </li></ul><ul><li>Can reduce costs </li></ul>

×