# data[].attributes.body
High-quality curriculum resources that are useful for the audience and help achieve business goals don't happen by chance. They are a result of skilled people following robust processes. A lot of the things that make something high-quality are invisible to people using it. We need to understand and use the processes that produce quality resources.
Consistent processes result in consistent quality of resources, and so the audience know what to expect when they see Te Poutāhū resources.

# data[].attributes.body
One of the most important aspects of design processes is to make sure we don't just to design our good ideas. Design processes help us get out of our heads (our brilliant ideas, our biases, our blind spots, our experiences) to produce something that is truly useful for our audiences - and isn't just what we think they need or what we think is good for them. If something is truly useful for the audience, we have more chance of users using it and more chance of us achieving the changes we want to achieve with the sector. I've read a couple of user experience experts who have said that education institutions are particularly bad at thinking they know what their audience wants but actually really misjudging this. Good user-centred design processes guard against this misunderstanding.

# data[].attributes.body
Other MoE teams that focus on design. For example, there is a service design team somewhere else in the MoE. We have to manage this engagement carefully so the scope of what we want to achieve is manageable.

# data[].attributes.headline
I think there needs to be layers - with broad representation in each of the layers - kind of like a 'working group', 'reference group/s' & 'approval group' model

# data[].attributes.subject
I think there needs to be layers - with broad representation in each of the layers - kind of like a 'working group', 'reference group/s' & 'approval group' model

# data[].attributes.body
Representatives across the team and ideally (this might not be possible) representatives of our users.

# data[].attributes.headline
A generalised process would be helpful but it needs to be adaptable by each team to suit their needs/processes with some 'do not pass go' checkpoints

# data[].attributes.subject
A generalised process would be helpful but it needs to be adaptable by each team to suit their needs/processes with some 'do not pass go' checkpoints

# data[].attributes.body
Design principles that are broad enough to work for all our teams. Be clear about what's not negotiable. Process documents would be useful, especially for newer team members, but they'd need to be able to adapt them for each of our contexts.

# data[].attributes.headline
I am not sure 'create' is the right word necessarily - we shouldn't try to re-invent the wheel - but we can collate the best principles and adapt them for our purposes, ensuring they are inclusive of all the work we do. 

# data[].attributes.subject
I am not sure 'create' is the right word necessarily - we shouldn't try to re-invent the wheel - but we can collate the best principles and adapt them for our purposes, ensuring they are inclusive of all the work we do. 

# data[].attributes.headline
The purpose of the resource/content and the outcomes we want to achieve

# data[].attributes.subject
The purpose of the resource/content and the outcomes we want to achieve

# data[].attributes.body
Te Tiriti o Waitangi

# data[].attributes.headline
Taking practical action to give effect to Te Tiriti o Waitangi

# data[].attributes.subject
Taking practical action to give effect to Te Tiriti o Waitangi

# data[].attributes.body
Who will be using this resource? How will it help them? What situation will they be in when they get this resource? Do they want this resource?

# data[].attributes.headline
The audience we are designing for in all their diversity

# data[].attributes.subject
The audience we are designing for in all their diversity