Blue 01

Accordion - Details variation (CSS-core)

Regular

Integrating content into agile workflows

Build content into the sprint from day one. Treat words as part of the product, not an afterthought. Add content tasks to the backlog and review them in stand ups alongside design and development.

Collaborate with product owners to define a clear Definition of Done for content. Encourage early reviews of copy within design critiques so language decisions move at the same pace as the interface.

  • Join daily stand ups and retrospectives to stay aligned
  • Include content tickets in sprint demos
  • Track feedback and updates using the same agile tools as your team
Designing simple paths through complex tasks

Start by naming the single outcome the user needs to achieve. Remove anything that doesn’t help them get there.

Structure the page like a conversation: set expectations up front, group related steps, and explain why you’re asking for information.

  • Lead with clear, task‑focused headings
  • Break long processes into confident, named steps
  • Use examples only where users typically hesitate
Partnering with subject matter experts

Make it easy for SMEs to help. Share a short agenda and a live doc. Ask them to walk a realistic scenario instead of describing the system.

Capture source links and who approved wording so changes are auditable. Follow up with a redline or prototype to make feedback fast.

  • Record facts with dates and owners
  • Translate jargon into plain language
  • Agree on the exact words users will see

Toggle controls

Embedding content design in agile delivery

Bring content into every stage of the sprint, not just the end. Treat it like any other design asset: plan it, review it, and test it early.

When copy and interface evolve together, teams avoid last‑minute rewrites and mismatched intent.

Making complex information easy to follow

Help users reach their goal quickly. Use strong verbs and avoid multi‑step sentences that hide the action.

  • Cut instructions down to what matters
  • Show one decision at a time
  • Keep headings short and concrete

Sometimes a simple label swap or reordered field makes the biggest difference.

Collaborating with subject matter experts

Ask SMEs to explain how people actually use a service, not just how it works on paper. Listen for pain points or unclear language that can inform your content choices.

Keep notes visible to everyone so edits don’t get lost. A few short comments are better than one long document review.

Follow up with a quick playback—what you heard, what will change, and what stays the same.


Accordion - Legacy variation JS

Regular

Sprint cadence or workflow

In your team there may already be a sprint cadence that includes content design. Become familiar with agile practices such as the Kanban wall, daily stand ups and sprint planning. Understand the user journey and their needs. Get involved in usability testing sessions and iteration.

Otherwise, the content workflow may be separate from the product team. At the very least, make sure the team has real content to use, when they’re building a prototype. Also ensure your team uses real content when it does usability testing. Attend playbacks from this testing, to know how your content needs to change.

As well as designing the user experience with product team members, a content designer works to know the facts with subject matter experts.

Simplifying complexity

Your aim from the outset is to simplify everything for the user. Your main task will be to set up a clear path for them to achieve their goal.

Start with a user story. You should create one for each piece of content, from user research. If you’re part of a multidisciplinary product team, everyone is likely to be using them as you design and build.

A user story will help you to pinpoint the user need from the outset. It puts the user front-of-mind and gives you a focus when designing and writing the content.

Next, create a structure for your page, based on the user story. Write up meaningful H2 headers to serve as signposts to help the user do what they need to do.

Working with subject matter experts

Share your way of working with your subject matter experts – in person if possible.

They're a great way of introducing your approach to a subject matter expert, which may be completely foreign to them. It will show them how you're focusing on the user, and what you're trying to solve. Ask them for feedback. Find out if there’s anything missing and if you’re on the right track.

Toggle controls

First Home Owner's Grant (New Homes) scheme (FHOG)

Buying or building your first home? You may be eligible for a $10,000 grant under the First Home Owner's Grant (FHOG) scheme.

This grant scheme only applies to buying or building a new home.

You can make a claim if:

  • your home is newly constructed and has a total value of less than $600,000
  • the land and the dwelling you intend to build has a combined value of less than $750,000.
HomeBuilder program

If you are building a new home, you could also be able to apply for the Australian Government grant of $25,000. To be eligible you must:

  • sign the contract between 4 June 2020 and 31 December 2020
  • commence within 3 months of the contract date.

HomeBuilder complements the NSW Government’s existing First Home Owner Grant and stamp duty concessions.

First Home Buyer Assistance scheme (FHBAS)

The NSW Government recently announced increased thresholds for purchases of new homes and vacant land to build a new home from 1 August 2020. The threshold for existing home purchases remains unchanged.

Accordion - Details variation (CSS-core)

Regular

Building rhythm in agile sprints

Plan content into each sprint so words evolve alongside design and development. Treat every ceremony—planning, review, retro—as a place to check content quality and intent.

  • Add content tasks to sprint boards
  • Review copy during design critiques
  • Demo final text in showcases

Keeping language visible in these moments prevents rushed edits at release time.

Guiding users through complex flows

Design with empathy for the reader. Show progress and group related steps logically so users never feel lost.

Explain actions briefly and remove obstacles. Use natural sequencing to create calm, predictable experiences.

Working alongside subject experts

SMEs bring the deep knowledge—your role is to shape it into something clear and helpful.

  • Prepare focused questions before meetings
  • Write collaboratively in a shared doc
  • Follow up with a short summary of what was agreed

Consistency builds trust and keeps content accurate over time.

Toggle controls

Sprint cadence or workflow

Join the team’s rhythm early. Be part of stand ups, planning sessions, and retros to spot content needs before they become blockers. Work closely with design and engineering to align intent and tone.

Keep a living content backlog and track it with the same tools your team uses for features. Make small, iterative improvements instead of waiting for a rewrite cycle.

Simplifying complexity

When something feels complicated, start by reframing it from the user’s point of view. Ask what they actually need to do, and make that your north star.

  • Define a clear primary action
  • Group related steps together
  • Explain why, not just how

Sometimes simplification isn’t about fewer words, but clearer structure.

Working with subject matter experts

SMEs are key partners, not gatekeepers. Meet with purpose—send questions beforehand and focus on decisions, not descriptions.

Keep a shared doc open during sessions to capture facts, approvals, and wording in real time. It saves endless back‑and‑forth later.

End each meeting with a summary of what was agreed and what’s next. This builds trust and keeps the process transparent.


Accordion - Legacy variation JS

Regular

Sprint cadence or workflow

In your team there may already be a sprint cadence that includes content design. Become familiar with agile practices such as the Kanban wall, daily stand ups and sprint planning. Understand the user journey and their needs. Get involved in usability testing sessions and iteration.

Otherwise, the content workflow may be separate from the product team. At the very least, make sure the team has real content to use, when they’re building a prototype. Also ensure your team uses real content when it does usability testing. Attend playbacks from this testing, to know how your content needs to change.

As well as designing the user experience with product team members, a content designer works to know the facts with subject matter experts.

Simplifying complexity

Your aim from the outset is to simplify everything for the user. Your main task will be to set up a clear path for them to achieve their goal.

Start with a user story. You should create one for each piece of content, from user research. If you’re part of a multidisciplinary product team, everyone is likely to be using them as you design and build.

A user story will help you to pinpoint the user need from the outset. It puts the user front-of-mind and gives you a focus when designing and writing the content.

Next, create a structure for your page, based on the user story. Write up meaningful H2 headers to serve as signposts to help the user do what they need to do.

Working with subject matter experts

Share your way of working with your subject matter experts – in person if possible.

They're a great way of introducing your approach to a subject matter expert, which may be completely foreign to them. It will show them how you're focusing on the user, and what you're trying to solve. Ask them for feedback. Find out if there’s anything missing and if you’re on the right track.

Toggle controls

First Home Owner's Grant (New Homes) scheme (FHOG)

Buying or building your first home? You may be eligible for a $10,000 grant under the First Home Owner's Grant (FHOG) scheme.

This grant scheme only applies to buying or building a new home.

You can make a claim if:

  • your home is newly constructed and has a total value of less than $600,000
  • the land and the dwelling you intend to build has a combined value of less than $750,000.
HomeBuilder program

If you are building a new home, you could also be able to apply for the Australian Government grant of $25,000. To be eligible you must:

  • sign the contract between 4 June 2020 and 31 December 2020
  • commence within 3 months of the contract date.

HomeBuilder complements the NSW Government’s existing First Home Owner Grant and stamp duty concessions.

First Home Buyer Assistance scheme (FHBAS)

The NSW Government recently announced increased thresholds for purchases of new homes and vacant land to build a new home from 1 August 2020. The threshold for existing home purchases remains unchanged.