...roles on offer. Accessibility is everyone’s responsibility Building an accessible and inclusive service is everyone’s responsibility and each delivery team member has a part to play. That’s why we’ve started...
...need to deliver services that work for everyone: Teams will build inclusive services that can be used by everyone who needs them – including those with disabilities or who lack...
...within CSOC. One of my main responsibilities is leading 5 shift teams of Security Operation Centre Analysts. These teams work every day of the year, 24 hours a day, 7...
...design practices. We’ve found that understanding the importance of accessible and inclusive government services is one thing but putting this into practice is another. While working as part of a...
...points thoroughly, steering the product team towards a prioritised roadmap, and delivering a product that users adore: one that makes their lives a tiny bit easier. Myth 2: Adding more...
...and/or operate aspects of their key technology services wherever appropriate. In many cases, such changes enable optimised economics, greater leverage of niche suppliers with deep subject matter expertise, better understanding...
...better when everyone is involved Don’t expect to see Researchers and Designers sitting behind desks all day, or to see long reports or design specifications. Our delivery teams need to...
...Global Entry is the US equivalent to Registered Traveller, providing automated entry through immigration and customs. Anyone that travels to the US regularly is likely to benefit as they will...
...BRP development we generated some technical debt, which created extra complexity and made it difficult for someone new to the codebase to quickly grasp the principles on which we had...
...way a private beta should be launched. The launch was combined with a user research field trip so we could test the system with these beta users. I’ve been on...
Recent Comments