Tags: gds

What’s the design process at GDS? | Government Digital Service

A look behind the scenes of gov.uk. I like their attitude to Photoshop comps:

We don’t want a culture of designs being “thrown over a wall” to a dev team. We don’t make “high fidelity mock ups” or “high fidelity wireframes”. We’re making a Thing, not pictures of a Thing.

And UX:

We don’t have a UX Team. If the problem with your service is that the servers are slow and the UX Team can’t change that, then they aren’t in control of the user experience and they shouldn’t be called the user experience team.

Paul Downey - just doodling - YouTube

A lovely little profile of Paul and his sketches.

The Web Is Agreement! The URI Is The Thing!

How many people are missing out on JavaScript enhancement? | Government Digital Service

The research behind GDS’s research that one in every 93 users of gov.uk is not receiving JavaScript …and it’s not because of JavaScript being disabled in their browser either. As ever, progressive enhancement is most useful in dealing with the situations you don’t anticipate.

Notes from dConstruct 2013 | Government Digital Service

Matt looks at this year’s dConstruct through the lens of GDS.

Progressive enhancement in the Government Service Design manual

A nice description of progressive enhancement by Norm, as applied at GDS.

We’re not ‘appy. Not ‘appy at all.

An excellent explanation from Tom Loosemore on why the Government Digital Service is putting its energy into open standards and the web, rather than proprietary native apps.