Skip to content

Add guidance on deciding how to deliver something#161

Open
owenatgov wants to merge 3 commits into
mainfrom
decide-what-to-deliver-guidance
Open

Add guidance on deciding how to deliver something#161
owenatgov wants to merge 3 commits into
mainfrom
decide-what-to-deliver-guidance

Conversation

@owenatgov

@owenatgov owenatgov commented Mar 13, 2026

Copy link
Copy Markdown
Contributor

Adds guidance for deciding how to deliver a change, which is suplemented by another new page on how we deliver the design system and an expansion of the white we do landing page to give more detail to our primary artefacts and how they fit together.

Closes #160

Originally worked on in this google doc (internal to the team only)

@netlify

netlify Bot commented Mar 13, 2026

Copy link
Copy Markdown

Deploy Preview for govuk-design-system-team-docs ready!

Name Link
🔨 Latest commit b7f2a94
🔍 Latest deploy log https://app.netlify.com/projects/govuk-design-system-team-docs/deploys/69c694ba5921460008d46b8e
😎 Deploy Preview https://deploy-preview-161--govuk-design-system-team-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@calvin-lau-sig7

Copy link
Copy Markdown
Contributor

My comments originally from Slack:

There's a lot here, you've really put a lot down! Are you planning to move this to a Google Doc for more commenting?

Anyway, I'll try to summarise my thoughts.

I think the idea of this page works. Did you work any of this off of the leads' Intro to the Design System deck? Might be useful to match those descriptions.

It'd also help keep the "What makes up the Design System" as short as possible and need-to-know, because...

The main show of this page is the "How we deliver the design system to our users". I know you're already doing it, but we can probably do more to be more "purpose-led" in the way we talk about what makes a Style/Component/Pattern.

And then guiding principles can be also be a snappier, action-led "Do this and remember"-type list of tips.

@owenatgov owenatgov force-pushed the decide-what-to-deliver-guidance branch from 3d2352d to a5d370f Compare March 27, 2026 14:17
@owenatgov owenatgov marked this pull request as ready for review March 27, 2026 14:28
@owenatgov owenatgov force-pushed the decide-what-to-deliver-guidance branch from a5d370f to b7f2a94 Compare March 27, 2026 14:31
@lewisdarlow-gds

Copy link
Copy Markdown
Contributor

I really like this @owenatgov thank you for putting it together. I had a couple of thoughts as I was reading it

The first few titles on the page are the opposite of one another (which I think is your intention)

e.g

  • Sometimes you need more than one thing
  • Take an MVP approach
    and
  • Don’t decide too early
  • It’s okay to change your mind

but these left me thinking if I was reading this new would It take me a while to consider which approach to take because they're the opposite?

I like how these are guiding principles I wonder if they should be more action based like the Government Design Principles https://www.gov.uk/guidance/government-design-principles and if we should list the principles after the first paragraph before you go into the content.

Small detail but on the paragraph 'If you can avoid new code, do so' the final full stop has an extra space before it.

Happy to chat about any of my feedback and thanks for sharing.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Documention on how to decide what form a new feature takes

3 participants