What are 'internet-era ways of working'?

    Tom Loosemore, formerly of the UK Government Digital Service (GDS) and Co-op Digital has founded a new organisation that advises governments large public organisations.

    That organisation, Public.digital, has defined ‘internet era ways of working’ which, as you’d expect, are fascinating:

    1. Design for user needs, not organisational convenience
    2. Test your riskiest assumptions with actual users
    3. The unit of delivery is the empowered, multidisciplinary team
    4. Do the hard work to make things simple
    5. Staying secure means building for resilience
    6. Recognise the duty of care you have to users, and to the data you hold about them
    7. Start small and optimise for iteration. Iterate, increment and repeat
    8. Make things open; it makes things better
    9. Fund product teams, not projects
    10. Display a bias towards small pieces of technology, loosely joined
    11. Treat data as infrastructure
    12. Digital is not just the online channel
    There's a wealth of information underneath each of these, but I feel like just these top-level points should be put on a good-looking poster in (home) offices everywhere!

    The only things I’d add from work smaller, but similar work I’ve done around this are:

    • Make your teams and organisation as diverse as possible
    • Ensure that your data is legible by both humans and machines
    But I'm nitpicking. This is great stuff.

    Source: Public.digital

    What are 'internet-era ways of working'?

    Tom Loosemore, formerly of the UK Government Digital Service (GDS) and Co-op Digital has founded a new organisation that advises governments large public organisations.

    That organisation, Public.digital, has defined ‘internet era ways of working’ which, as you’d expect, are fascinating:

    1. Design for user needs, not organisational convenience
    2. Test your riskiest assumptions with actual users
    3. The unit of delivery is the empowered, multidisciplinary team
    4. Do the hard work to make things simple
    5. Staying secure means building for resilience
    6. Recognise the duty of care you have to users, and to the data you hold about them
    7. Start small and optimise for iteration. Iterate, increment and repeat
    8. Make things open; it makes things better
    9. Fund product teams, not projects
    10. Display a bias towards small pieces of technology, loosely joined
    11. Treat data as infrastructure
    12. Digital is not just the online channel
    There's a wealth of information underneath each of these, but I feel like just these top-level points should be put on a good-looking poster in (home) offices everywhere!

    The only things I’d add from work smaller, but similar work I’ve done around this are:

    • Make your teams and organisation as diverse as possible
    • Ensure that your data is legible by both humans and machines
    But I'm nitpicking. This is great stuff.

    Source: Public.digital