background preloader

GOV.UK – GDS design principles

GOV.UK – GDS design principles
We should share what we’re doing whenever we can. With colleagues, with users, with the world. Share code, share designs, share ideas, share intentions, share failures. The more eyes there are on a service the better it gets — howlers are spotted, better alternatives are pointed out, the bar is raised. Much of what we’re doing is only possible because of open source code and the generosity of the web design community. We should pay that back.

Related:  .GOV.UKe-learningPublic innovation

Most of government is mostly service design most of the time. Discuss. – Matt Edgar writes here Without exception, everyone I meet in the public sector wants to help make their service better. Most of them are in some way frustrated. The domain is massive and the activities disjointed. People engaged in any given service – from users and frontline workers down to managers and policymakers – can go for months on end without coming into contact with each other. On the rare occasions they do meet, they generally do so with mutual incomprehension.

Designing Education: Educating Design User Experience Magazine The concept of design in not new to education. However, the act of designing as we understand it in user experience—or design thinking—is not yet mainstream in the design for teaching and learning. The pervasiveness of technology and the maturity of both user-centered design and e-learning are intertwining design and education in deeper ways. Until not long ago, all classroom settings were static and very much the same: a desk and a blackboard for the educator, books, papers, tables, and chairs for the students. Educators worked in a closed environment where it was enough for them to know their subject matter and how to teach it. Now, the ongoing introduction of technology in the classroom (audiovisual, computers, Internet access, tablets, and more) has led to many new elements and, therefore, the need to orchestrate them.

HTTP: The Protocol Every Web Developer Must Know – Part 1 HTTP stands for Hypertext Transfer Protocol. It's a stateless, application-layer protocol for communicating between distributed systems, and is the foundation of the modern web. As a web developer, we all must have a strong understanding of this protocol. Let's review this powerful protocol through the lens of a web developer.

Service design phases — Government Service Design Manual Accessible Media Player by Nomensa The timeline slider below uses WAI ARIA. Please use the documentation for your screen reader to find out more. Learning Experience Design - The Most Valuable Lessons This article, the one that you are reading, is part of a learning experience. Learning experiences aren’t a matter of classroom delivery – they are any interaction with a user/customer/individual in which the person is going to learn something (which we hope you will in this article). Products contain a vast array of potential learning experiences from learning the interface, how best to interact with the product, to information provided and through help and support and onboarding too.

Eight options for a radical innovation policy “It’s good as far as it goes, but it’s not very radical.” People often say this when the Government, or for the matter the Opposition, publish any sort of innovation policy proposal. It’s usually a fair comment. British innovation policy has been pretty technocratic and steady-as-she-goes for 20 years and more. You’d be hard-pressed to find much difference between the views of the three main Westminster parties when it comes to innovation. So how about a bit of radicalism? HTTP: The Protocol Every Web Developer Must Know – Part 2 In my previous article, we covered some of HTTP's basics, such as the URL scheme, status codes and request/response headers. With that as our foundation, we will look at the finer aspects of HTTP, like connection handling, authentication and HTTP caching. These topics are fairly extensive, but we'll cover the most important bits. A connection must be established between the client and server before they can communicate with each other, and HTTP uses the reliable TCP transport protocol to make this connection. By default, web traffic uses TCP port 80.

OMG standards - Formal Specifications This page provides a summary of OMG specifications that have either been formally published or are in the finalization process. The "specification" column is used to locate the directory structure on the OMG document server that serves as the "home" for all documents related to that specification. Click the Specification title to be taken to that specification's main page. | Business Modeling | CORBA and Middleware | CORBAservices | CORBA security | CORBA Embedded Intelligence | DDS | | Language Mappings | ISO Adopted Specifications | Modeling and Metadata | Modernization | | Domain Specifications | Signal- and Image-Processing | CORBA/IIOP Specifications CORBA / Specialized Specifications

Features of agile — Government Service Design Manual Some common features of the agile development methods we’ve used at GDS. Sprints Sprints are about planning what you and your team will achieve and when you will achieve it by. Each member of your team should have a task to complete within each sprint. Each sprint is of equal length and usually lasts between 1 to 2 weeks, but you can use longer or shorter sprints in your project. When deciding the length of your sprints, consider: Why You Need to Connect with Your Peers in the E-Learning Community I’m a big fan of community and how it helps us learn from each other. This is especially important for those of us in the elearning industry. If you are a financial analyst, odds are that there are a number of seasoned financial analysts in your organization who could draw from their experience and offer you all sorts of tips. Often that’s not true for elearning.

MacArthur Foundation Research Network Today’s society is characterized by a set of complex problems – such as inequality, climate change and affordable access to healthcare – that are seemingly intractable. People have looked to traditional societal institutions – like government agencies and advocacy groups – to tackle these problems, and they have become frustrated by the inability of these institutions to act effectively and legitimately. Unsurprisingly, trust in existing institutions is at an all-time low. Advances in technology together with new scientific insights on collaboration and decision-making provide for a unique opportunity to redesign our democratic institutions and make them more legitimate and effective.

Line-mode browser dev days at CERN CERN wants to bring the line-mode browser experience back to life so that people can step back in time and relive what it was like to browse the web in the very early days. No images, no colours, no clicking – just content. An unimpressive medium to a modern audience, the line-mode browser is nevertheless one of the key cultural assets associated with the story of how the web began.

Testing in an agile environment — Government Service Design Manual The basics of any testing approach still apply in the agile world, but the aim of testing can be quite different. It’s important to recognise you are testing in the first place to: build the best quality system you can make sure it does what the customer requires complete it at a cost that everyone agrees can be afforded (cost being money, business change, risk etc) How to Create a Leaderboard for eLearning with Google “Gamification.” We recognize the benefits (even through all the hype) and we would like to add it to our courses. But where to begin? It is not enough just to add a game to your course. We need a way to make it social. After all, bragging rights go a long way towards reinforcing learning.

Related:  digital strategieswebontwerpAnimation, Support et débats Politique relatifs au numérique