Difference between revisions of "Surge Team"
John.ryan21 (talk | contribs) |
John.ryan21 (talk | contribs) |
||
Line 23: | Line 23: | ||
=='''<big><big><big>The Surge Team</big></big></big>'''== | =='''<big><big><big>The Surge Team</big></big></big>'''== | ||
− | <big><big>Established at the Canada School of Public Service in 2018, the Surge Team supports policy projects where quick action or breakthroughs are needed. We do not have ongoing files. Instead, we collaborate on time-limited projects with partners at | + | <big><big>Established at the Canada School of Public Service in 2018, the Surge Team supports policy projects where quick action or breakthroughs are needed. We do not have ongoing files. Instead, we collaborate on time-limited projects with partners at CSPS and across the federal public service.</big> |
<br> | <br> | ||
<br> | <br> | ||
Line 50: | Line 50: | ||
|- | |- | ||
|style=min-width:250px; max-width:400px|<big><big>'''Next Steps & Reflections'''</big></big> | |style=min-width:250px; max-width:400px|<big><big>'''Next Steps & Reflections'''</big></big> | ||
− | <big>Offering support to put ideas into effect, and capturing lessons learned to | + | <big>Offering support to put ideas into effect, and capturing lessons learned to apply to future work</big> |
|[[File:6-9_brain.png|frameless|upright=0.5]] | |[[File:6-9_brain.png|frameless|upright=0.5]] | ||
|[[File:4-6_speech_bubble.png|frameless|upright=0.5]] | |[[File:4-6_speech_bubble.png|frameless|upright=0.5]] | ||
|style=min-width:250px; max-width:400px|<big><big>'''Engagement & Briefing'''</big></big> | |style=min-width:250px; max-width:400px|<big><big>'''Engagement & Briefing'''</big></big> | ||
− | <big>Validating possible solutions | + | <big>Validating possible solutions by engaging with stakeholders, and generating products that tell a compelling story</big> |
|} | |} | ||
<br clear="all"> | <br clear="all"> | ||
− | <big><big>'''We offer a range of policy services''', | + | <big><big>'''We offer a range of policy services''' to meet our partners' needs, including:</big></big> <br> |
− | <br> | ||
{| width="70%" cellpadding="10" cellspacing="15px" | {| width="70%" cellpadding="10" cellspacing="15px" | ||
Line 138: | Line 137: | ||
|style=text-align:center;background:#627dd0;color:#FFFFFF|<big><big>'''Conclude'''</big></big> | |style=text-align:center;background:#627dd0;color:#FFFFFF|<big><big>'''Conclude'''</big></big> | ||
|- | |- | ||
− | |style=text-align:left;background:#FDF0C7|<big>- '''Explain''' our service model <br>- '''Learn''' about your needs <br>- '''Discuss''' objectives, scope, and timelines | + | |style=text-align:left;background:#FDF0C7|<big>- '''Explain''' our service model <br>- '''Learn''' about your needs <br>- '''Discuss''' objectives, scope, and timelines</big> |
− | |style=text-align:left;background:#cdeaeb|<big>- '''Discuss''' specific deliverables and identify key stakeholders <br>- '''Determine''' roles and responsibilities <br>- '''Agree''' on | + | |style=text-align:left;background:#cdeaeb|<big>- '''Discuss''' specific deliverables and identify key stakeholders <br>- '''Determine''' roles and responsibilities <br>- '''Agree''' on project scope and schedule through a '''Memorandum of Understanding'''</big> |
− | |style=text-align:left;background:#ccc5e1|<big>- '''Evaluate''' progress and incorporate feedback | + | |style=text-align:left;background:#ccc5e1|<big>- '''Evaluate''' progress and incorporate feedback <br>- '''Revise''' deliverables, scope, and timelines as needed to meet objectives</big> |
|style=text-align:left;background:#d2daf2|<big>- '''Close out''' deliverables <br>- '''Discuss''' project transition period <br>- '''Share lessons learned''' to promote continuous learning</big> | |style=text-align:left;background:#d2daf2|<big>- '''Close out''' deliverables <br>- '''Discuss''' project transition period <br>- '''Share lessons learned''' to promote continuous learning</big> | ||
|} | |} | ||
<br> | <br> | ||
− | <big><big>As a team, '''we work in a series of short sprints and deep dives''' to improve the quality of products. Our work is '''iterative''' and '''collaborative''', | + | <big><big>As a team, '''we work in a series of short sprints and deep dives''' to improve the quality of products. Our work is '''iterative''' and '''collaborative''', allowing us to learn equally from failures and successes. Consulting with stakeholders is a critical part of how we do our work. At the same time, '''our projects are often non-linear''', redefining problem statements and generating more research as we move forward and change course as needed.</big></big> |
[[File:Approaching work.png|center|frameless|upright=3]] | [[File:Approaching work.png|center|frameless|upright=3]] | ||
<br clear="all"> | <br clear="all"> | ||
Line 165: | Line 164: | ||
{| width="80%" cellpadding="10" cellspacing="15px" | {| width="80%" cellpadding="10" cellspacing="15px" | ||
|style=background:#358083|[[File:3.1calendar.svg|center|frameless|upright=0.5]] | |style=background:#358083|[[File:3.1calendar.svg|center|frameless|upright=0.5]] | ||
− | |style=background:#cdeaeb|<big>'''Online Transition Planner and Checklist: A | + | |style=background:#cdeaeb|<big>'''Online Transition Planner and Checklist: A Tool to Support Government Transition'''</big> |
''<big>Partnership with the Privy Council Office</big>'' | ''<big>Partnership with the Privy Council Office</big>'' | ||
− | Centralized a checklist of tasks to be completed for all incoming and outgoing Ministers, staff, and offices | + | - Centralized a checklist of tasks to be completed for all incoming and outgoing Ministers, staff, and offices |
− | Deployed a Software-as-a-Service (SaaS) tool across the GC | + | - Deployed a Software-as-a-Service (SaaS) tool across the GC |
− | Provided an enterprise-wide view of transition activities for the Privy Council Office | + | - Provided an enterprise-wide view of transition activities for the Privy Council Office |
|- | |- | ||
|style=background:#627DD0|[[File:3.2bubble.svg|center|frameless|upright=0.5]] | |style=background:#627DD0|[[File:3.2bubble.svg|center|frameless|upright=0.5]] | ||
Line 179: | Line 178: | ||
''<big>Partnership with the Policy Community Partnerships Office, Privy Council Office, and Behavioural Insights Team</big>'' | ''<big>Partnership with the Policy Community Partnerships Office, Privy Council Office, and Behavioural Insights Team</big>'' | ||
− | Applied a team-based learning-by-doing approach to teach public servants about Behavioral Insights and make concrete progress on real problems | + | - Applied a team-based learning-by-doing approach to teach public servants about Behavioral Insights and make concrete progress on real problems |
− | Combined expert-led training and one-on-one support to develop BI-based interventions for real world challenges | + | - Combined expert-led training and one-on-one support to develop BI-based interventions for real world challenges |
|- | |- | ||
|style=background:#4e3f78|[[File:3.3book.svg|center|frameless|upright=0.5]] | |style=background:#4e3f78|[[File:3.3book.svg|center|frameless|upright=0.5]] | ||
Line 187: | Line 186: | ||
''<big>Partnership with Health Canada</big>'' | ''<big>Partnership with Health Canada</big>'' | ||
− | Primer for public servants on the need for reconciliation and the role they can play | + | - Primer for public servants on the need for reconciliation and the role they can play |
− | Developed in consultation with Indigenous public servants and policy experts | + | - Developed in consultation with Indigenous public servants and policy experts |
− | Content contributed to the app [https://www.csps-efpc.gc.ca/tools/apps/ils/index-eng.aspx Reconciliation: A Starting Point] | + | - Content contributed to the app [https://www.csps-efpc.gc.ca/tools/apps/ils/index-eng.aspx Reconciliation: A Starting Point] |
|- | |- | ||
|style=background:#358083|[[File:3.4table.svg|center|frameless|upright=0.5]] | |style=background:#358083|[[File:3.4table.svg|center|frameless|upright=0.5]] | ||
Line 197: | Line 196: | ||
''<big>Partnership with Transport Canada</big>'' | ''<big>Partnership with Transport Canada</big>'' | ||
− | Curation of tools and resources relevant to public engagement that will support TC's Transformation Plan | + | - Curation of tools and resources relevant to public engagement that will support TC's Transformation Plan |
− | Provides a public engagement framework in prototype format that articulates 5 broad phases of engagement and explores best practices | + | - Provides a public engagement framework in prototype format that articulates 5 broad phases of engagement and explores best practices |
|- | |- | ||
|style=background:#627DD0|[[File:3.5plume.svg|center|frameless|upright=0.5]] | |style=background:#627DD0|[[File:3.5plume.svg|center|frameless|upright=0.5]] | ||
Line 206: | Line 205: | ||
''<big>Partnership with Employment and Social Development Canada</big>'' | ''<big>Partnership with Employment and Social Development Canada</big>'' | ||
− | Research and | + | - Research and analysis to support pre-drafting process (how to tell a good story through an MC) |
− | Strategic advice and Surge capacity for coordinating a horizontal MC | + | - Strategic advice and Surge capacity for coordinating a horizontal MC |
− | Curated tools and resources to support drafting process | + | - Curated tools and resources to support drafting process |
|- | |- | ||
|style=background:#4e3f78|[[File:3.6flow.svg|center|frameless|upright=0.5]] | |style=background:#4e3f78|[[File:3.6flow.svg|center|frameless|upright=0.5]] | ||
Line 216: | Line 215: | ||
''<big>Partnership with Employment and Social Development Canada</big>'' | ''<big>Partnership with Employment and Social Development Canada</big>'' | ||
− | Engagement of 12 federal organizations to identify practices for more consistent and meaningful performance measurement | + | - Engagement of 12 federal organizations to identify practices for more consistent and meaningful performance measurement |
− | Stock-take of data and briefing materials to support the adoption of a new logic model | + | - Stock-take of data and briefing materials to support the adoption of a new logic model |
− | Development of practices for viable disaggregated data collection and reporting | + | - Development of practices for viable disaggregated data collection and reporting |
|} | |} | ||
Line 304: | Line 303: | ||
==<div id="Contact">'''<big><big>Contact Us</big></big>'''== | ==<div id="Contact">'''<big><big>Contact Us</big></big>'''== | ||
− | <big><big>If you are interested in working with us or want to learn more about what we do reach out to us at surgesolutionsunit@csps-efpc.gc.ca or visit our [https://gcxgce.sharepoint.com/teams/1000611/ GCXchange site].</big></big> | + | <big><big>If you are interested in working with us or want to learn more about what we do, reach out to us at surgesolutionsunit@csps-efpc.gc.ca or visit our [https://gcxgce.sharepoint.com/teams/1000611/ GCXchange site].</big></big> |
Revision as of 12:42, 17 April 2023
How We Can Help | How We Work | Who We've Helped | FAQ | Contact Us |
---|
For best results please view this page on a desktop browser The Surge TeamEstablished at the Canada School of Public Service in 2018, the Surge Team supports policy projects where quick action or breakthroughs are needed. We do not have ongoing files. Instead, we collaborate on time-limited projects with partners at CSPS and across the federal public service.
|
|
|
|
|
How We Work
Our approach is most effective with engaged and collaborative partners: we use regular touchpoints throughout the project to build off your expertise and respond to your needs.
Discuss | Design a Plan | Develop and Deliver | Conclude |
- Explain our service model - Learn about your needs - Discuss objectives, scope, and timelines |
- Discuss specific deliverables and identify key stakeholders - Determine roles and responsibilities - Agree on project scope and schedule through a Memorandum of Understanding |
- Evaluate progress and incorporate feedback - Revise deliverables, scope, and timelines as needed to meet objectives |
- Close out deliverables - Discuss project transition period - Share lessons learned to promote continuous learning |
As a team, we work in a series of short sprints and deep dives to improve the quality of products. Our work is iterative and collaborative, allowing us to learn equally from failures and successes. Consulting with stakeholders is a critical part of how we do our work. At the same time, our projects are often non-linear, redefining problem statements and generating more research as we move forward and change course as needed.
Who We've Helped
Since December 2018, we have worked with several organizations to deliver over 50 projects with more than 150 individual deliverables. You can find details on these projects, as well as lessons we've learned from them, on our GCXchange site.
Our projects touch on many policy areas, including public administration and machinery of government, Indigenous relations, national security, social policy, and innovation, among others.
Examples of Projects:
Online Transition Planner and Checklist: A Tool to Support Government Transition
Partnership with the Privy Council Office - Centralized a checklist of tasks to be completed for all incoming and outgoing Ministers, staff, and offices - Deployed a Software-as-a-Service (SaaS) tool across the GC - Provided an enterprise-wide view of transition activities for the Privy Council Office | |
Behavioural Insights Blended Services Pilot: Facilitated Workshop Learning
Partnership with the Policy Community Partnerships Office, Privy Council Office, and Behavioural Insights Team - Applied a team-based learning-by-doing approach to teach public servants about Behavioral Insights and make concrete progress on real problems - Combined expert-led training and one-on-one support to develop BI-based interventions for real world challenges | |
Reconciliation Primer: Policy Brief and Learning Tool
Partnership with Health Canada - Primer for public servants on the need for reconciliation and the role they can play - Developed in consultation with Indigenous public servants and policy experts - Content contributed to the app Reconciliation: A Starting Point | |
Modern Public Engagement: Facilitated Discussions and Engagement Framework Development
Partnership with Transport Canada - Curation of tools and resources relevant to public engagement that will support TC's Transformation Plan - Provides a public engagement framework in prototype format that articulates 5 broad phases of engagement and explores best practices | |
Memorandum to Cabinet Process
Partnership with Employment and Social Development Canada - Research and analysis to support pre-drafting process (how to tell a good story through an MC) - Strategic advice and Surge capacity for coordinating a horizontal MC - Curated tools and resources to support drafting process | |
Renewed Horizontal Performance Measurement Framework
Partnership with Employment and Social Development Canada - Engagement of 12 federal organizations to identify practices for more consistent and meaningful performance measurement - Stock-take of data and briefing materials to support the adoption of a new logic model - Development of practices for viable disaggregated data collection and reporting |
Testimonials:
|
|
|
|
|
|
|
FAQ
How many projects does Surge normally take on?
Typically, 2-4 projects at any given time, with start and end-dates staggered.
What is the average duration of a project? How many analysts work on a project?
Projects usually last from 2 to 8 months. A project team will typically include 3-5 analysts. We do not 'loan out' analysts to departments, unlike the Free Agent Program.
How does the cost sharing approach to projects work?
CSPS and the partner department sign an MOU outlining costs, roles, timelines and deliverables. Costs are based on analysts' hourly wages and any additional O&M costs, if applicable (e.g., costs to hire an external speaker).
All partner projects are cost-shared - CSPS takes on a certain portion of the project costs (based on discussions and agreement with partners). Funds are collected through an Interdepartmental Settlement, typically from partners' O&M budgets.
How long does the MOU take to put in place?
We can normally draft and share an MOU quickly (1-2 weeks), after scope, timelines, and deliverables have been discussed and agreed upon.
Contact Us
If you are interested in working with us or want to learn more about what we do, reach out to us at surgesolutionsunit@csps-efpc.gc.ca or visit our GCXchange site.