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

add 'check eligibility cost time' pattern #359

Closed
wants to merge 1 commit into from

Conversation

HarryTrimble
Copy link

@HarryTrimble HarryTrimble commented Feb 20, 2017

Check eligibility, cost and time

Multiple page task pattern

(screenshots below)

Before deciding to use a service users need to know:

  • if they’re eligible or have to use it?
  • how much it costs or how much they’ll get?
  • how long they have to wait?

The pattern can help provide users with answers they need. It does this by:

  • asking users questions
  • automatically calculate the answer
  • show user answer specific to them

We tested and iterated this pattern with 46 users over 6 rounds of research. Users doing a variety of things: becoming childminders, getting environmental permits, learning to drive and transporting goods in vans and lorries.

Many services already have users answer questions to check they're eligible, ready or want to use it.

check-eligibility-cost-time-question

check-eligibility-cost-time-result

@HarryTrimble HarryTrimble force-pushed the add-check-eligibility-cost-time-pattern branch from 6129101 to 7b0338c Compare February 20, 2017 14:29
@HarryTrimble
Copy link
Author

The JavaScript routes in docs/documentation_routes.js might need to be easier to read and change

@joelanman
Copy link
Contributor

Hi @HarryTrimble thanks for doing this. It seems to use an old method of keeping data from page to page, in the query string. We're hoping to merge #340 soon, which does the same thing but uses session. Would it be possible to see if your work can use that instead?

</main>
{% endblock %}

<!-- application fee calculator
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you remove this commented section?

@joelanman
Copy link
Contributor

I think this could also do with some instructions on how to see the different paths. As someone not familiar with this work I'm clicking random answers to try and see the different states.

@edwardhorsford
Copy link
Contributor

This feels a like a complete prototype included in the kit rather than sample pages for other to use. I think it could be reworked a bit to make it easier to use, and then link off to an example.

It looks like there are a few new basic page types included in this:

  • Eligible page
  • Ineligible page
  • Cost page
  • Time page
  • any others?

Suggest we have a single summary page about the pattern in the kit, linking to relevant guidance (blog post / hackpad / service manual?), and linking to the sub page types in the kit. This could link off to an external prototype that is an example of this pattern being used.


What do others think? Might help to get together and discuss.

@HarryTrimble
Copy link
Author

HarryTrimble commented Mar 1, 2017

Hey @joelanman @edwardhorsford

@timpaul has suggested we link out to tested bigger examples people can download

Examples page in prototype kit:

examples link from prototype kit

Links to

separate app

Separate app people can try and download

Give examples their own repos on AlphaGov

@HarryTrimble
Copy link
Author

HarryTrimble commented Mar 10, 2017

@joelanman @edwardhorsford @edwardhorsford and Alice our product manager decided this pattern would be better as guidance in the Service Manual, which links to a prototyped example. Migrate it to the pattern library was it's up and running.

I've drafted what the guidance and prototype could be like

Should maybe close the pull request

@joelanman joelanman closed this Apr 26, 2017
@kr8n3r kr8n3r deleted the add-check-eligibility-cost-time-pattern branch November 6, 2018 09:07
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.

4 participants