Search

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.

Transactional services lead to a change in government-held records, typically involving an exchange of information, money, licences or goods.

Examples of transactional services include:

• submitting a claim
• registering a business
• updating contact details
• lodging a tax return

1. Pre-discovery: scope and plan the project: 
2. Discovery: explore the problem in more detail and engage with stakeholders to understand their needs.
3. Alpha: generate ideas for solutions and develop prototypes to test with stakeholders.
4. Beta: build out the preferred prototype and refine it through further testing.
5. Live: implement the solution and conduct regular evaluation or review.