Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore how future iterations of Forms, other products in the pipeline (possibly Service Builder) and the Design System overlap. #4436

Open
Tracked by #4401
Katrina-Birch opened this issue Jan 13, 2025 · 0 comments

Comments

@Katrina-Birch
Copy link
Contributor

Katrina-Birch commented Jan 13, 2025

What?

Some government services are simple and straightforward processes (from the users perspective, not accounting for back office processes), for example, Apply for a deceased person's service record (MOD) which could potentially be built using Forms with more features. Service owners often find it hard to recruit developers with the right coding expertise to maintain legacy systems. Maintaining a full cohort of developers with the right coding expertise is expensive.

So what?

As a service owner, I need a way for my team to build, maintain and improve the service in a way that doesn't require a lot of coding knowledge so that I can run the team as cost effectively as possible.

What now?

Explore how future iterations of Forms, other products in the pipeline (possibly Service Builder) and the Design System overlap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant