Coleman appointed government deputy for digital engagement

Government IT

Coleman appointed government deputy for digital engagement

Kathleen Hall

Emer Coleman is to join the Government Digital Service team as deputy director of digital engagement.

Coleman has been director of digital projects at the Greater London Authority (GLA) for the past two years. During that time, she was responsible for the development of the London Datastore, a project to release all of London's public sector data into the public domain. She will join the Cabinet Office Government Digital Service (GDS) team in January and will report to Mike Bracken, director of digital at GDS.

“Emer’s appointment will raise our game as we develop more products and services with partners and developers inside and outside government," said Bracken. "Emer’s experience in government, and particularly in freeing up transport data and her work at the Greater London Authority, means we have another great talent at the Government Digital Service.”

Coleman said: “I hope my experience in London will benefit GDS as it continues its journey to embed digital by default across the whole of government. I am grateful for the opportunity to be part of revolutionising government digital services, if not a little daunted to say the least.”

The appointment is part of GDS’ move to bulk up its team with the creation of 28 new positions. In September, Bracken told Computer Weekly that GDS is expected to have up to 200 people in its team.

Coleman said she did not currently know who her successor at GLA will be.


Email Alerts

Register now to receive ComputerWeekly.com IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.
 

COMMENTS powered by Disqus  //  Commenting policy