Search

The policy toolkit describes a process for developing whole-of-government digital policies, but it can also help you develop a range of other instruments to achieve policy intent.  

While policy work can lead to a wide range of solutions and instruments, it’s important not to start with any one solution in mind.  

The policy toolkit templates and resources are specific to building policy, but the design practices can be applied or adapted to suit almost any problem that you need to solve. 

1. Designing tech policy is a journey, not a destination: just like technology, good tech policy is agile and constantly evolving.
2. An outcome well defined is a problem half-solved: a clear articulation of the desired policy outcome is at the heart of all good tech policy design.
3. Good tech policy is responsive and timely, it creates clarity and certainty: effective communication is critical.
4. Consultation is a theme, not a step: when designing tech policy, consult often, transparently, and widely.
5. Be responsive, foster feedback loops: tech policy can be contentious and consensus is not always possible, but it is important to demonstrate all voices have been heard and considered.
6. Regulation should not be the default, consider all available options: choose the most proportionate and fit-for-purpose solution (remember: bad ideas do exist).
7. Context matters, good tech policy is not designed in isolation: consider how proposed solutions will impact and interact with adjacent systems and jurisdictions (domestically and internationally).
8. Revision and refinement are strengths, not weaknesses: the end of the tech policy design process is just the beginning: implementation, evaluation and review are vital next steps.