Ausspc 2010 Presentation Building Lob Solutions With Share Point 2010


Published on

This presentation was delivered at the SharePoint 2010 Conference. It presents key factors for building line of business solutions using ECM technologies.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Opening slide please include
  • Provocations: All content should be process-centric The future of site orientation is not social. Facebook only will be a disaster. Conversations are a means to an end. What percentage of a corporation’s activities are driven by altruism or self-actualisation vs make a profit? So its dollars which make a difference, and business processes are all about making them (ie. maximise revenue) or conserving them (effectiveness and efficiency – note that effectiveness should pretty much always be first) Social interactions about a company are driven by one of two things: Ethical positioning OR questions about products and services. Reputation is primarily built around quality and consistency. All of these things are process outcomes. Conversations are a process.
  • You need a purpose and focus for any ECM implementation. Without purpose and focus you cannot get stakeholder buy in nor meaningful collective action leading to an outcome. Criteria for inclusion is meeting or exceeding initial expectations, and a consensus opinion of success. Note that only 5% of highly successful projects Data drawn from a survey of 90+ projects in 83 companies.
  • In this example there are 2 workflows at play: The workflow associated with reporting and managing incidents Content approval associated with checking in new or revised policies into Sharepoint document libraries The incident reporting workflow is by far the more complex. The last point on this slide – orientation on ongoing improvement, is important, and something which can be done in every organisation and just about every workflow. The incident investigation process results in recommendations. We could observe cynically many of these would just sit on the shelf. A logical extension to the workflow is managing recommendations, explicitly approving or rejecting each in turn. The same principle can be applied to any process, if you provide the ability for participants to make suggestions for improvement, which are then explicitly reviewed and either accepted or rejected.
  • Ausspc 2010 Presentation Building Lob Solutions With Share Point 2010

    1. 2. Building Line of Business Solutions Using SharePoint 2010 ECM Technology <ul><li>Simon Rawson / Milan Gross </li></ul>
    2. 3. What We’ll Discuss this Session <ul><li>Anatomy of business processes and content </li></ul><ul><li>Common components of LOB solutions </li></ul><ul><li>Business value </li></ul><ul><li>SharePoint 2010 ECM features which help </li></ul><ul><li>Implications for SharePoint practitioners </li></ul>
    3. 4. Highly Successful Projects Process Effectiveness v Efficiency – LOB Focussed
    4. 5. Components of a LOB Solution <ul><li>Process oriented </li></ul><ul><li>Transactions and tasks – workflow and information architecture </li></ul><ul><li>Support </li></ul><ul><li>Metrics, reporting, and performance analysis </li></ul><ul><ul><li>Individual </li></ul></ul><ul><ul><li>Collective </li></ul></ul><ul><ul><li>Operational (BAM) </li></ul></ul><ul><ul><li>Management </li></ul></ul><ul><li>Evolving – the need for feedback and constant improvement </li></ul><ul><li>Retention and reproduction </li></ul>
    5. 6. Line of Business Scenario – OH&S <ul><li>Delivery infrastructure Sharepoint – using native features </li></ul><ul><li>Incident reporting – web form </li></ul><ul><li>Notification / approval – Sharepoint triggered </li></ul><ul><li>Document (report) generation & management </li></ul><ul><li>Status check about key incident stages </li></ul><ul><li>Managed metadata and filtering </li></ul><ul><li>Performance measurement, metrics and auditability </li></ul><ul><li>Retention and disposal </li></ul>
    6. 7. OHS Scenario <ul><li>Show some cool things </li></ul>
    7. 8. OHS Scenario – The Bottom Line <ul><li>Use the strengths of the software – they are ‘benefit enablers’ – to get more value from your investment </li></ul><ul><li>Process automation, process measurement and content management go hand in hand – know thy knowledge management infrastructure </li></ul><ul><li>The process manages outcomes through to completion, including review and remediation / improvement – a best practice recommendation </li></ul>
    8. 9. Process maturity <ul><li>Ensure the solution provides a small stretch </li></ul><ul><li>Stages </li></ul><ul><ul><li>Initial </li></ul></ul><ul><ul><li>Repeatable </li></ul></ul><ul><ul><li>Managed </li></ul></ul><ul><ul><li>Mapped </li></ul></ul><ul><ul><li>Measured </li></ul></ul><ul><ul><li>Optimised </li></ul></ul><ul><li>Prototype it and engage stakeholders at all levels </li></ul><ul><li>Evolution approach to processes </li></ul>
    9. 10. Best practice summary <ul><li>Shift focus of finalisation to the client (staff person) </li></ul><ul><li>Keep people in the loop </li></ul><ul><li>Think broadly about the process stakeholders – there are always more than you realise </li></ul><ul><li>Think of workflow as spanning systems and workgroups </li></ul><ul><li>Provide documentation and support </li></ul><ul><li>Always monitor / manage outcomes </li></ul><ul><li>Track metrics – and measure ongoing benefit </li></ul>
    10. 11. Best practice summary <ul><li>Take an iterative approach to process development </li></ul><ul><li>Involve process participants </li></ul><ul><li>Think about the ‘benefit enablers’ – benefits you engineer using SharePoint strengths </li></ul><ul><li>Document assumptions – they impact benefits </li></ul><ul><li>Take care of the culture – organisational change management & training </li></ul><ul><li>Build in a generic ‘suggestion box’ process through which participants can raise suggestions </li></ul>
    11. 12. Managed Innovation / Suggestions ACTION Suppliers Staff Customers Business Partners
    12. 13. Managing Innovation <ul><li>Ideas, suggestions, problems, comments </li></ul><ul><li>Initial screening review. Escalate valuable ideas (or critical problems) </li></ul><ul><li>Periodic review for the remainder </li></ul><ul><li>Outcome is approval, parking or additional research </li></ul><ul><li>Approval requires budget and project management </li></ul><ul><li>Monitor progress, outcomes and benefits – use dashboards and scorecarding </li></ul><ul><li>Provide recognition - rewards and feedback </li></ul>
    13. 14. Managed Innovation CSFs <ul><li>Senior management support and an innovation policy </li></ul><ul><li>A new management process – good change management and communications </li></ul><ul><li>Budgets, resourcing, goals and planning turns ideas into action </li></ul><ul><li>Advertise the wins and track accumulated benefits Recognition and feedback completes the loop – and powers an upward spiral </li></ul><ul><li>The technology is the lesser part of the programme </li></ul>
    14. 15. Thank you to our Sponsors