Tech Policy
Process
- Tech Policy Principles
- Tech, Digital and Cyber Responsibilities
- Tech Explainers
- Tech Policy Timeline
The objective of this module is to set out a best practice process to guide the design of tech policy.
The design of policy is often messy, and rarely linear. This module sets out the various steps involved in tech policy design. We aim to enhance accessibility and participation in the process by lifting the veil and revealing the actors, outputs, pathways and diversions that can occur during the design cycle. This module was developed in consultation with public servants, industry, and civil society. We thank the Australian Government’s Digital Technology Taskforce and the Tech Council of Australia for supporting this module and the consultations.
Ultimately, ‘tech policy’ is just ‘policy’. Further resources on policy design are available at the Australian Public Service Commission’s Policy Hub: Introduction to delivering great policy.
Purpose statement
Create a future in which people, technology and the planet thrive.
Define the Outcome
Principles
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.
Designing tech policy is a journey, not a destination
Just like technology, good tech policy is agile and constantly evolving.
Good tech policy is responsive and timely, it creates clarity and certainty
Effective communication is critical.
Consultation is a theme, not a step
When designing tech policy, consult often, transparently, and widely.
Be responsive, foster feedback loops
Tech policy can be contentious, consensus is not always possible, but demonstrate all voices have been heard and considered.
Lead Actors
Australian Public Service (APS) lead policy department (at own initiative or as directed by Minister/Cabinet) or Industry/NGO/Civil Society
Steps One to Three can occur external to the APS but, unless robust, will reset to Step One when the APS is tasked to initiate the policy proposal
What is the desired outcome?
What is the problem or opportunity the outcome is trying to solve or harness?
Why is government intervention needed? What is new or novel about the tech? How are the existing frameworks not working to take into account the disruption? What are the gaps/deficiencies the outcome seeks to address?
What specific tech expertise is needed to understand the problem or opportunity? Who holds that expertise?
Who is the policy lead within government? Where does the authority to act/head of power lie? (In Australia the Administrative Arrangement Orders (AAO) formally allocate executive responsibility among ministers and set out which matters and legislation fall within the responsibility of which government department or portfolio).
Who are the key stakeholders (across government, industry (large and small), civil society (individuals and organisations))?
Can you answer each Question?
Can you prepare each Output?
Identify the Options
Principles
Regulation should not be the default, consider all available options
Choose the most proportionate and fit-for-purpose solution (remember: bad ideas do exist).
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).
Designing tech policy is a journey, not a destination
Just like technology, good tech policy is agile and constantly evolving.
Good tech policy is responsive and timely, it creates clarity and certainty
Effective communication is critical.
Consultation is a theme, not a step
When designing tech policy, consult often, transparently, and widely.
Be responsive, foster feedback loops
Tech policy can be contentious, consensus is not always possible, but demonstrate all voices have been heard and considered.
Lead Actors
Australian Public Service (APS) lead policy department (at own initiative or as directed by Minister/Cabinet) or Industry/NGO/Civil Society
Steps One to Three can occur external to the APS but, unless robust, will reset to Step One when the APS is tasked to initiate the policy proposal
What options are available?
Is regulation the best option to achieve the desired outcome? Are there other means that could achieve the outcome more efficiently and effectively?
Does a solution already exist? Has the problem already been solved? Are there existing tools (including in different or adjacent domains) that could be applicable? Is there precedent (domestically and internationally)?
What evidence is available to support an assessment of the effectiveness of the options?
Have you consulted experts and stakeholders to identify all viable options, including not regulating?
Can you answer each Question?
Can you prepare each Output?
Assess the Options
Principles
Regulation should not be the default, consider all available options
Choose the most proportionate and fit-for-purpose solution (remember: bad ideas do exist).
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).
Designing tech policy is a journey, not a destination
Just like technology, good tech policy is agile and constantly evolving.
Good tech policy is responsive and timely, it creates clarity and certainty
Effective communication is critical.
Consultation is a theme, not a step
When designing tech policy, consult often, transparently, and widely.
Be responsive, foster feedback loops
Tech policy can be contentious, consensus is not always possible, but demonstrate all voices have been heard and considered.
Lead Actors
Australian Public Service (APS) lead policy department (at own initiative or as directed by Minister/Cabinet) or Industry/NGO/Civil Society
Steps One to Three can occur external to the APS but, unless robust, will reset to Step One when the APS is tasked to initiate the policy proposal
What is the likely net benefit of each option, including no action?
Are the benefits proportionate and fit-for-purpose? Will the options deliver the outcome? Do the benefits of the outcome justify the means?
How will the options interact with existing domestic regulation? Are the options consistent with prevailing international approaches? If not, has the rationale for departure been explained?
How will the option impact adjacent and interdependent domains? What are the possible/likely unintended consequences of the options?
Will the options provide regulatory certainty for investors and business?
How could the options be abused or misused? What safeguards are needed?
What are the budget implications? Is budget available? Can offsets be identified? Are new monies required?
Taking into account all of the above, what is the best option from those you have considered?
Can you answer each Question?
Can you prepare each Output?
If yes, is the preferred option not to regulate?
Advice to Government
Principles
Regulation should not be the default, consider all available options
Choose the most proportionate and fit-for-purpose solution (remember: bad ideas do exist).
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).
Designing tech policy is a journey, not a destination
Just like technology, good tech policy is agile and constantly evolving.
Good tech policy is responsive and timely, it creates clarity and certainty
Effective communication is critical.
Consultation is a theme, not a step
When designing tech policy, consult often, transparently, and widely.
Be responsive, foster feedback loops
Tech policy can be contentious, consensus is not always possible, but demonstrate all voices have been heard and considered.
Lead Actors
Australian Public Service (APS) lead policy department, in consultation with Ministerial Offices
What Intra- and Inter-Departmental Committees need to approve the recommended option? Have approvals been given?
Is budget approval required? If so, what cycle applies? Has budget been secured?
How will the chosen option be implemented and evaluated?
Does the decision require new legislation or regulatory instruments to implement? Does existing legislation already provide authority? Would other policy mechanisms suffice (grants process, codes, rules, guidelines)?
How will the recommendation be communicated to stakeholders? Have stakeholders been advised as transparently as possible about the chosen option and the rationale behind the decision?
Does any information gathered in Steps One – Four need to be protected (national security or commercial confidentiality)? The default should be disclosure. Have the reasons for non-disclosure been explained as transparently as practicable?
Can you answer each Question?
If yes, does the recommended option require Intra- or Inter-Departmental Approval?
If no, does the recommended option require new monies?
Can you prepare each Output?
Decision Government Chooses Tool
Principles
Regulation should not be the default, consider all available options
Choose the most proportionate and fit-for-purpose solution (remember: bad ideas do exist).
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).
Designing tech policy is a journey, not a destination
Just like technology, good tech policy is agile and constantly evolving.
Good tech policy is responsive and timely, it creates clarity and certainty
Effective communication is critical.
Consultation is a theme, not a step
When designing tech policy, consult often, transparently, and widely.
Be responsive, foster feedback loops
Tech policy can be contentious, consensus is not always possible, but demonstrate all voices have been heard and considered.
Lead Actors
Minister/Cabinet
Australian Public Service (APS) lead policy department may change after Step Five
Who has the authority to approve the recommended option? Does the power rest with an individual Minister, several Ministers, or Cabinet? Has approval been given?
Has approval been given?
Has each Output been produced?
If yes, is the agreed option not to regulate?
If no, does the agreed option require a legislative process?
Draft the Legislation
Principles
Be responsive, foster feedback loops
Tech policy can be contentious, consensus is not always possible, but demonstrate all voices have been heard and considered.
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).
Designing tech policy is a journey, not a destination
Just like technology, good tech policy is agile and constantly evolving.
Good tech policy is responsive and timely, it creates clarity and certainty
Effective communication is critical.
Consultation is a theme, not a step
When designing tech policy, consult often, transparently, and widely.
Lead Actors
Consultation and drafting instructions: Australian Public Service (APS) lead policy department, in consultation with Minister’s office
Legislative drafting: Office of Parliamentary Counsel (OPC)
Has the policy owner changed? Is the policy owner also the solution owner?
What is the case for action? What protections, safeguards, and reviews need to be built in?
Do drafters need technology-specific expertise to support drafting? If so, who is best placed to provide this independently?
Can you answer each Question? Has the relevant Executive Approval been given for drafting?
Has each Output been produced?
Consultation on Draft
Principles
Be responsive, foster feedback loops
Tech policy can be contentious, consensus is not always possible, but demonstrate all voices have been heard and considered.
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).
Designing tech policy is a journey, not a destination
Just like technology, good tech policy is agile and constantly evolving.
Good tech policy is responsive and timely, it creates clarity and certainty
Effective communication is critical.
Consultation is a theme, not a step
When designing tech policy, consult often, transparently, and widely.
Lead Actors
Consultation and drafting instructions: Australian Public Service (APS) lead policy department, in consultation with Minister’s office
Legislative drafting: Office of Parliamentary Counsel (OPC)
Has a consultation communication plan been developed (to illicit input from a broad range of stakeholders, not just those involved in previous steps)?
Do consultation time frames allow for stakeholders to provide considered input? Are there particular reasons for urgency justifying shorter consultation time? If so, has this rationale been communicated clearly to stakeholders?
Are there other adjacent submissions/consultations scheduled within this time frame? How will this impact stakeholder capacity to provide considered input? Does the imperative of the outcome justify this impost? If so, has the imperative been explained to stakeholders?
Will there be opportunities for formal and informal stakeholder engagement during this period, to facilitate targeted, comprehensive, and considered written submissions?
Can you answer each Question?
Have you prepared each Output?
Revise and Finalise Draft
Principles
Be responsive, foster feedback loops
Tech policy can be contentious, consensus is not always possible, but demonstrate all voices have been heard and considered.
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).
Designing tech policy is a journey, not a destination
Just like technology, good tech policy is agile and constantly evolving.
Good tech policy is responsive and timely, it creates clarity and certainty
Effective communication is critical.
Consultation is a theme, not a step
When designing tech policy, consult often, transparently, and widely.
Lead Actors
Consultation and drafting instructions: Australian Public Service (APS) lead policy department, in consultation with Minister’s office
Legislative drafting: Office of Parliamentary Counsel (OPC)
Has the draft been revised in light of the consultations?
Has a Stakeholder Feedback Plan been developed (to provide feedback on key themes from consultations and submissions, including advice on how input provided shaped amendments to the draft, and rationale for why the input was/was not incorporated)?
Can you answer each Question?
If yes, did new information emerge during the consultations that necessitates revisiting Steps Two, Three, and Five?
Have you prepared each Output?
Bill Introduced to Parliament
Principles
Be responsive, foster feedback loops
Tech policy can be contentious, consensus is not always possible, but demonstrate all voices have been heard and considered.
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).
Designing tech policy is a journey, not a destination
Just like technology, good tech policy is agile and constantly evolving.
Good tech policy is responsive and timely, it creates clarity and certainty
Effective communication is critical.
Consultation is a theme, not a step
When designing tech policy, consult often, transparently, and widely.
Lead Actors
Minister, Cabinet, or Parliament, in consultation with Australian Public Service (APS) lead policy department and Office of Parliamentary Counsel (OPC)
Click here for an overview of the process once a Bill is introduced to Parliament.
Does the Bill have sufficient support to pass Parliament?
If no, proceed to
Bill Approved by Parliament
Principles
Be responsive, foster feedback loops
Tech policy can be contentious, consensus is not always possible, but demonstrate all voices have been heard and considered.
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).
Designing tech policy is a journey, not a destination
Just like technology, good tech policy is agile and constantly evolving.
Good tech policy is responsive and timely, it creates clarity and certainty
Effective communication is critical.
Consultation is a theme, not a step
When designing tech policy, consult often, transparently, and widely.
Lead Actors
Minister, Cabinet, or Parliament, in consultation with Australian Public Service (APS) lead policy department and Office of Parliamentary Counsel (OPC)
Has the Output been produced?
Implementation, Evaluation, and Review
Principles
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.
Designing tech policy is a journey, not a destination
Just like technology, good tech policy is agile and constantly evolving.
Good tech policy is responsive and timely, it creates clarity and certainty
Effective communication is critical.
Consultation is a theme, not a step
When designing tech policy, consult often, transparently, and widely.
Lead Actors
Australian Public Service (APS) Implementation Lead
Implementation lead may be different to lead policy department
What structures need to be established to implement the approved proposal? This could include, but is not limited to, codes, rules, guidelines, subordinate legislation, or grants program.
How can stakeholders be leveraged in support of this?
What processes can be incorporated into implementation to encourage openness and transparency in implementation and evaluation?
How will progress toward the outcome be measured? What information and systems do you need to put in place now to support this?
Where/how will baseline metrics be gathered (to measure impact and change over time)?
Can you answer each Question?
Have you prepared each Output?