Opportunities and Services:
- Sharing the established expertise of faculty innovators as advice or guidance (i.e. consulting).
- Providing research services and research collaboration.
Utilizing software to assist with policy thinking.
- literature reviews
- jurisdictional scans
- document reviews
- systematic evidence collection
- policy evaluations
- stakeholder perspectives (surveys, interviews, focus groups)
Facilitating workshops and planning sessions around policy solutions and approaches.
- content analysis (e.g. NVivo)
- geographic information systems (e.g. ArcMap)
- social network analysis (e.g. NodeXL)
- causal mapping (e.g. STELLA)
- scenario analysis (e.g. HIVE)
- infographics (e.g. piktochart)
Connecting partners to other faculty, services, and programs at MUN (and to other partners).
- persona development (i.e. user characterization)
- design sprints (i.e. the diverge-emerge-converge model)
- system modelling
- prototyping, testing, and experimenting
- challenging current understandings and perceptions
Delivering access to the content of scholarly literature through summaries and synthesis.
- e.g. EPI is connected to the natural sciences through its association with Grenfell’s School of Science and Environment
Offering methodological support for partners conducting their own research projects.
While much of EPILab’s activities are likely to be “ad-hoc” or “one-off”, certain partnered arrangements around the above opportunities and services will be treated as formal projects. Such projects will vary by whether they are short-term (i.e. days to weeks) or long-term (months to years), whether they are service-oriented (i.e. where EPILab does work requested by the partner) or co-productive (i.e. where EPILab and the partner collaborate throughout), and whether the details of the project are even known at the outset or not (i.e. open-ended projects).
Regardless of its type, any formal project should be based on a written agreement between the partners, which could be as short as one page for simple projects. This agreement should specify, at minimum:
- the partner organizations and their respective project leads or liaisons
- a basic title and description of the project
- the specific tasks required as well as an indication of who will carry them out
- estimated costs and whether additional funding will be necessary
- if so, either provided by a partner at the outset or applied for as an initial task
- funding is more likely to be necessary for long-term projects
- a proposed timeline or list of milestones
- an estimation of outputs, specifying how each partner (and society) will benefit
- e.g. EPI is a research institute and thus benefits from research-related outputs
- but the focus here is still primarily on benefits to the partner and society