Kelly Lee

Making the change itself is easy. Understanding how we want teams to use the header and in which circumstances is more complex.

TLDR: very powerful, and meets our needs fully. Ability to build form interfaces making it easier to upload data. Concerns about the accessibility (no focus state). We could automate features...

There may be collaboration with folks external to the team, eg Jonathan in IA team.

Preferable to buy a tool that can do this rather than build it ourselves (this would be an additional cycle, with more developers in the squad).

We'll have daily stand ups, with one longer stand up once a week for more in-depth conversations. We'll have a dedicated Slack channel for conversations. We'll have a more in-depth...

This is based on the assumption that collecting this data is valuable to the team, therefore has value in being repeatable framework.

**Questions from mid-cycle demo:** - Should we speak to Uzma Razaq (GDS ResearchOps manager) who may have budget for tools we could use for this? - Have we considered a...

TLDR: simple database without ability to build form interfaces. Not as powerful as Airtable. Also has accessibility issues with the focus state.

Summary of our chat about processes we use to collect information on services: - collection of information and analysis will be a small story, not another brief (ie 3 week...

We decided to just duplicate the content.