Chapter 19: Community Mapping Research Design

Chapter Overview

This chapter provides a structured approach to designing rigorous, ethical Community Mapping research. Research design is the architecture of inquiry — the plan that connects questions to methods, methods to data, and data to conclusions. In Community Mapping, research design must integrate community priorities, multiple methods, power analysis, and long-term relationships into a coherent plan. This chapter walks through the essential components of designing research that is credible, ethical, participatory, and useful.

Learning Outcomes

By the end of this chapter, you will be able to:

Define research design and explain its role in Community Mapping projects
Formulate clear, answerable research questions grounded in community priorities
Define the scope and boundaries of a Community Mapping research project
Identify relevant stakeholders and distinguish stakeholder mapping from power mapping
Select appropriate methods based on research questions, community context, and available resources
Build a research plan that integrates timelines, resources, ethics, and risk assessment
Apply the Research Design Template to structure a Community Mapping project

Key Terms

Research Design: The structured plan connecting research questions, methods, data collection, analysis, and community review into a coherent inquiry process.
Scope: The boundaries of what a research project will and will not address, including geographic area, time period, populations, and research questions.
Stakeholder: Any person, group, or institution with an interest in or influence over the research process or outcomes.
Community Review: The non-negotiable practice of sharing research findings with the community for validation, interpretation, and consent before publication or external use.

19.1 Asking the Right Question

Research design begins with a question. Not just any question — the right question. The right question is clear, answerable, important to the community, and within your capacity to address with integrity.

Community Mapping research questions typically take one of several forms:

Descriptive questions ask what exists. Where are the youth services? How many seniors live alone? What assets do residents identify in their neighborhood? Descriptive questions produce maps, inventories, and profiles. They are essential baselines but rarely sufficient on their own.

Relational questions ask how things connect. Do neighborhoods with more parks have lower rates of chronic disease? Are service deserts correlated with transit access? How do social networks shape access to employment? Relational questions reveal patterns, correlations, and potential leverage points.

Explanatory questions ask why patterns exist. Why do some neighborhoods have abundant services while others have few? What historical decisions shaped current inequities? Why do residents avoid certain public spaces? Explanatory questions require qualitative depth — interviews, document review, historical analysis — not just spatial data.

Evaluative questions ask how well something is working. Does the new community hub serve its intended population? Are outreach efforts reaching isolated seniors? Is the food security initiative reducing barriers? Evaluative questions support accountability, learning, and course correction.

Participatory questions ask what the community wants to know. What do youth think would make their neighborhood safer? Where do elders wish they could go but cannot? What do residents see as the most urgent need? Participatory questions center community knowledge and priorities, not researcher assumptions.

The best Community Mapping research questions are:

Clear and specific. "Improving food access" is not a research question. "Where do low-income households without cars live relative to grocery stores, and what transportation barriers do they face?" is a research question.
Answerable with available or obtainable data. A question requiring proprietary data you cannot access, or methods you do not have the skills or resources to implement, is not answerable. Adjust the question or acknowledge the gap.
Important to the community. Research that serves only academic curiosity or funder requirements, with no relevance to community wellbeing, is extractive. Co-develop questions with community partners.
Ethical to pursue. Some questions should not be asked. Mapping undocumented immigrants, mapping locations of survivors of domestic violence, mapping sacred sites without consent — these questions cause harm. Ethics comes before inquiry.

As Chapter 1.4 introduced, Community Mapping is applied research. The goal is not just to know — it is to support community action, decision-making, and equity. A good research question leads somewhere useful.

19.2 Defining Scope

Once you have a clear question, define the scope — the boundaries of what your research will and will not address. Scope includes:

Geographic area. Are you mapping a neighborhood, a municipality, a watershed, a region? Boundaries matter. A city-defined neighborhood may not match residents' sense of community. An administrative boundary may cut through a natural community. Be explicit about why you chose the boundaries you did — and acknowledge when boundaries are contested or arbitrary.

Time period. Are you mapping current conditions, change over time, or projected futures? If mapping change, over what time span? Historical mapping requires archival research and oral history. Futures mapping requires scenarios and forecasting. Current-state mapping requires up-to-date data and validation.

Populations. Are you mapping the whole community or specific populations (seniors, youth, newcomers, people experiencing homelessness)? Be clear. A map claiming to represent "the community" but based only on survey respondents or service users is incomplete.

Research questions. If your project began with multiple questions, which ones are in scope for this phase? Trying to answer every question at once leads to shallow work. Prioritize. Sequence. Be honest about what you will not address.

Methods. What methods are feasible given your timeline, budget, skills, and community relationships? A full household survey may be ideal but unaffordable. Walking interviews may be rich but slow. Secondary data analysis may be fast but limited. Choose methods that fit your scope — or adjust your scope to fit realistic methods.

Resources. What do you have? Time, funding, staff, volunteers, technology, expertise, community partnerships. What do you need? Be specific. Scope creep — the slow expansion of a project beyond its original boundaries — is a common failure mode. Guard against it by defining scope clearly and revisiting it regularly.

Scope is not fixed forever. Research is iterative. Findings from early phases may lead you to expand, narrow, or pivot. But changes in scope must be deliberate, documented, and communicated to partners and funders. A scope defined up front protects you from overcommitment and helps manage expectations.

19.3 Choosing the Community

The language "choosing the community" is dangerous. Outsiders rarely choose a community in any meaningful sense. Communities choose whether to engage with researchers — or not.

More accurate framing: Where will this research happen, and who invited you?

If you are a researcher from outside the community, you do not choose. You are invited — or you are not. The invitation may come from a community organization, a local government partner, a resident group, or a coalition. The invitation establishes the legitimacy of your presence and the terms of engagement. Without an invitation, you are conducting research on a community, not with it — and that raises serious ethical concerns.

If you are a resident, staff member, or long-term partner already embedded in the community, you still do not unilaterally decide to "map the community." You consult. You ask: Is this useful? Who should be involved? What are the risks? Who will benefit? Community Mapping that skips these conversations — even when done by insiders — can cause harm, breach trust, or serve the wrong priorities.

Even with an invitation, ask: Who issued the invitation? A municipal planner may invite you to map a neighborhood, but do residents know? Do they consent? A nonprofit director may invite you to map service gaps, but do clients have a say? An invitation from institutional gatekeepers is not the same as community consent. Build broader engagement.

The question is not "which community should I map?" The question is "which community relationships do I have — or can I ethically build — that would support collaborative inquiry?" If the answer is "none," do not proceed. Build relationships first. Or choose a different project.

For students and early-career researchers, this can feel frustrating. You need a project. You have a deadline. But Community Mapping is not a laboratory experiment you can set up on demand. It is a relational practice that takes time, humility, and reciprocity. If you cannot build those relationships, map something else — or partner with someone who already has them.

19.4 Identifying Stakeholders

Stakeholders are any person, group, or institution with an interest in or influence over the research process or outcomes. In Community Mapping, stakeholder identification is essential — but it is not the same as power mapping (covered in Chapter 5.9).

Common stakeholder categories:

Residents and community members. The people who live in the area being mapped. They hold lived experience, local knowledge, and the greatest stake in how findings are used. They are not a monolithic group — they include diverse ages, incomes, languages, abilities, and perspectives.

Community organizations. Nonprofits, faith groups, cultural associations, mutual aid networks, advocacy coalitions. They often have trust, reach, and on-the-ground knowledge that researchers lack.

Service providers. Health clinics, schools, social services, childcare centers, libraries, food banks. They see patterns of need, barriers, and gaps. They may be potential partners in data collection or users of findings.

Local government. Municipal staff (planners, public health, parks, transit), elected officials. They control resources, policy, and infrastructure decisions. They may be funders, partners, or audiences for advocacy.

Funders. Foundations, government agencies, or institutions providing financial support. They have expectations about deliverables, timelines, and accountability. They may shape scope and priorities.

Researchers and academic partners. If the project involves a university or research institution, clarify roles, ownership, and authorship up front.

Private sector actors. Businesses, developers, landlords. They may be data sources (e.g., business directories) or stakeholders if findings could affect their interests.

Indigenous governments and organizations. If the research takes place on Indigenous territory, Indigenous governments are not just stakeholders — they hold sovereignty and authority. Research must follow protocols established by the nation, including free, prior, and informed consent. OCAP principles (Ownership, Control, Access, Possession) apply to all Indigenous data (introduced in Chapter 9.9).

Stakeholder identification is not just listing names. It requires asking:

Who will be affected by this research?
Who holds power to act on findings?
Who holds knowledge essential to the research?
Who might be harmed if data is misused?
Who is missing from this list?

As Chapter 11.12 introduced, stakeholder mapping is a tool to visualize relationships, influence, and interest. A simple stakeholder map might plot actors on two axes: power to influence outcomes (low to high) and interest in the issue (low to high). This reveals who needs deep engagement (high power, high interest), who needs information (low power, high interest), and who requires monitoring (high power, low interest).

But stakeholder mapping is not power mapping. Power mapping (Chapter 5.9) analyzes structural power, historical advantage, and systemic inequities. Stakeholder mapping is narrower: who matters for this project? The two overlap but are not identical. A powerful actor may have no interest in your research. A marginalized community may have high interest but low formal power. Design engagement strategies accordingly.

19.5 Selecting Methods

Method selection flows from your research question, scope, stakeholders, and resources. Chapter 19 does not teach individual methods in depth — that is the work of Chapters 20-25. This section establishes principles for choosing methods.

Match methods to questions. Descriptive questions (what exists?) often use secondary data analysis, asset inventories, and GIS mapping. Relational questions (how do things connect?) require spatial analysis, network mapping, and statistical methods. Explanatory questions (why?) require qualitative methods: interviews, focus groups, document analysis, ethnography. Evaluative questions (how well is it working?) require baseline and follow-up data, often mixed methods.

Use multiple methods. As Chapter 1.4 emphasized, triangulation — using multiple sources of evidence — strengthens credibility. A finding supported by census data, service provider interviews, and resident focus groups is more robust than a finding from one source alone. Mixed methods also serve different audiences: quantitative data persuades funders and policymakers; stories persuade the public and media.

Center community voice. Participatory methods — community workshops, photovoice, resident-led surveys, walking audits — ensure that residents are co-researchers, not just data sources. Even when using secondary data, participatory validation (asking residents: does this match your experience?) is essential.

Consider accessibility. Can your methods reach people who are marginalized, isolated, or excluded? Online surveys miss people without internet. English-only focus groups miss newcomers. Daytime workshops miss people working multiple jobs. Design inclusive methods or acknowledge who is missing.

Plan for data integration. If you are collecting quantitative and qualitative data, how will you bring them together? A map showing service deserts is more powerful when combined with resident stories about the barriers they face. Plan integration early — don't bolt it on at the end.

Work within your capacity. A research design requiring advanced GIS skills you do not have, or 200 interviews you cannot complete in the timeline, is not realistic. Scale methods to fit capacity — or build capacity before starting. Overpromising and underdelivering damages trust.

Assess risk. Some methods carry risks. Mapping sensitive locations (safe houses, harm reduction sites, LGBTQ+ gathering spaces) can expose people to danger. Interviewing people in public housing about landlord neglect can trigger retaliation. Asking undocumented immigrants about their needs can put them at risk if data is not secured. Choose methods that minimize harm.

Common method combinations in Community Mapping research:

Secondary data + participatory validation: Use census, service directories, and administrative data to create baseline maps, then validate with community workshops.
Surveys + interviews: Surveys provide breadth (how many, how much), interviews provide depth (why, how, what does it mean).
GIS analysis + story mapping: Quantitative spatial analysis reveals patterns; story mapping adds lived experience and meaning.
Asset mapping + needs assessment: Mapping strengths and gaps together avoids deficit-only narratives.
Walking audits + institutional data: Residents observe and document conditions; institutions provide historical or policy context.

Chapter 5's systems thinking framework (5.1-5.8) is also a method — mapping relationships, feedback loops, and leverage points. Systems mapping is particularly powerful for understanding how services, policies, and community assets interact.

19.6 Building a Research Plan

A research plan is the blueprint. It specifies what you will do, in what order, by when, with whom, and using what resources. A good research plan is detailed enough to guide action but flexible enough to adapt when conditions change.

Essential components:

Phases and milestones. Break the research into phases: design, data collection, analysis, validation, reporting, action. Within each phase, identify milestones: "community partnership agreement signed," "baseline data collected," "draft findings validated with residents."

Tasks and responsibilities. Who does what? If this is a team project, assign roles clearly. If you are working with community partners, document who holds responsibility for recruitment, data collection, interpretation, and reporting. Avoid assumptions.

Timeline. Build a realistic timeline with buffer time. Community work takes longer than you expect. Recruiting focus group participants, coordinating schedules, translating materials, building trust — all take time. Academic researchers on semester schedules often underestimate this. Add 20-30% buffer to every estimate.

Data collection plan. For each method, specify: sample size or target participants, recruitment strategy, location, timeline, materials needed, consent procedures, and data storage.

Analysis plan. How will you analyze each data type? Quantitative data: what software, what statistical methods? Qualitative data: coding framework, thematic analysis, member checking? Spatial data: what layers, what analysis (proximity, clustering, overlay)? Plan analysis before data collection — it shapes what data you need.

Community review process. Non-negotiable. Plan at least one (preferably two) rounds of community review: once after preliminary findings, once before final publication. Community review is not "member checking" or "validation" — it is collaborative interpretation. Residents see patterns you miss. They catch errors. They reframe findings. They decide what is safe to share publicly and what is not.

Ethics and consent procedures. If working with human subjects, specify consent processes, data security, confidentiality protections, and harm-reduction measures. If working with Indigenous communities, specify how you will follow OCAP principles and the nation's research protocols.

Dissemination plan. How will findings be shared? Academic paper? Community report? Public presentation? Maps posted online? Social media? Plan formats, audiences, and timelines. Ensure community partners have access to findings in usable formats before external publication.

Contingency plans. What if recruitment fails? What if a partner withdraws? What if data is unavailable? What if findings are politically sensitive? Think through risks and have backup plans.

A research plan is a living document. As you move through the project, you will adjust timelines, refine methods, and respond to what you learn. Update the plan regularly and share updates with partners. Transparency builds trust.

19.7 Timeline and Resources

Realistic timelines and resource planning prevent failure. Community Mapping research is often slower and more resource-intensive than researchers expect.

Timeline considerations:

Relationship-building time. If you do not have existing relationships with community partners, add months (not weeks) for introductions, trust-building, and partnership negotiation. Community organizations are busy. They receive many research requests. They have been burned by extractive researchers before. Earning trust takes time.
Ethical review time. If your research requires institutional ethics review (Research Ethics Board, Institutional Review Board), plan for 4-8 weeks minimum, often longer. Include time for revisions if the board requests changes.
Community timelines, not academic timelines. Communities do not operate on semester schedules. Summer may be when youth are available but families are traveling. Winter may be hard for rural communities with limited transportation. Ramadan, Christmas, harvest season, pow wow season — all affect availability. Ask partners about timing.
Data access delays. Requesting data from government agencies, institutions, or organizations can take weeks or months. Some data requires formal agreements. Some data is never released. Plan early and have alternatives.
Translation and accessibility time. If materials must be translated, budget time and money. If events must be accessible (ASL interpretation, childcare, transportation), budget time to arrange.
Analysis time. Qualitative analysis is slow. Reading transcripts, coding, identifying themes, member checking — it takes weeks, not days. Quantitative analysis can be fast if you know the tools, but learning new software or methods takes time.
Community review time. Do not schedule community review meetings during the final week before your deadline. Partners need time to review materials, consult with their communities, and prepare feedback. Give at least two weeks, preferably four.

Resource considerations:

Funding. What will this cost? Staff time, participant honoraria, translation, printing, technology, travel, space rental, food for meetings, childcare, data licensing fees. If you have no funding, scale your project accordingly or seek funding before starting.
Staff and volunteers. Who will do the work? If relying on volunteers (including community volunteers), recognize that people have other commitments. Turnover happens. Plan for it.
Technology and tools. Do you have access to GIS software, survey platforms, transcription tools, data storage? If using community-owned devices or shared computers, ensure access and training.
Expertise. Do you have the skills needed? If not, will you build them (takes time) or hire/partner with someone who has them (costs money)?
Space. Where will you meet with community partners? Hold focus groups? Conduct workshops? Space costs money or requires relationships with institutions willing to share space.
Participant compensation. Best practice: compensate community members for their time, knowledge, and participation. Honoraria (cash, gift cards, meals) recognize that research extracts value from participants' labor. Budget for this.

A common mistake: assuming that because Community Mapping is "community-based," it will be cheap or free. It is not. Ethical, participatory research requires investment. If you do not have resources, be honest about what you can realistically accomplish — and adjust scope accordingly.

19.8 Risk Assessment

Every research project carries risks. Community Mapping research — because it involves people, power, and place — carries particular risks that must be assessed and mitigated.

Risks to participants:

Breach of confidentiality. If participant identities or sensitive information are exposed, people can face harm: retaliation from employers or landlords, family conflict, legal consequences, or social stigma. Risk is highest for marginalized populations: undocumented immigrants, people involved in criminalized activities, survivors of violence, LGBTQ+ people in hostile contexts.
Emotional harm. Interviews or focus groups about trauma, loss, discrimination, or violence can re-traumatize participants. Researchers must provide support resources, allow participants to skip questions, and debrief carefully.
Community conflict. Mapping can reveal tensions or inequities within a community, triggering conflict between groups. For example, a map showing that one neighborhood receives more services than another can inflame resentment. Anticipate and plan for mediation.

Risks to the community:

Misuse of data. Maps can be weaponized. A map showing where vulnerable people live can support targeted services — or enable policing, eviction, or surveillance. A map of informal economies can support policy reform — or trigger enforcement. Control who has access to sensitive data.
Extractive research. If researchers take data and leave without giving back findings, capacity, or support, the community has been exploited. This is not risk mitigation — it is basic ethics. Plan for reciprocity and community benefit.
Stigmatization. A map framing a neighborhood only through deficits (poverty, crime, blight) reinforces stigma and harms residents. Balance asset and needs mapping. Frame findings carefully.

Risks to researchers:

Safety risks. Fieldwork in unfamiliar areas, interviews in isolated locations, or research on sensitive topics (gang violence, political corruption) can pose physical risks. Conduct safety assessments. Work in pairs. Have check-in protocols.
Legal risks. In some jurisdictions, documenting certain activities (informal housing, undocumented workers, harm reduction sites) could expose researchers to legal liability. Consult legal expertise if needed.
Emotional toll. Researchers exposed to stories of trauma, poverty, or injustice can experience vicarious trauma. Build peer support, debriefing, and self-care into the research plan.

Risks to partnerships:

Breach of trust. If researchers violate agreements, miss deadlines, or publish findings without consent, partnerships are damaged — often permanently. This harms not just the current project but future researchers seeking to work in that community.
Power imbalances. Academic or institutional researchers hold structural power over community partners (credentials, funding, publication control). If not addressed, power imbalances lead to extractive dynamics. Name the power imbalance and build accountability structures.

Mitigation strategies:

De-identify data. Remove names, addresses, and identifying details. Aggregate data where possible.
Secure data storage. Encrypted files, password-protected devices, restricted access.
Informed consent. Clear, accessible explanations of risks, benefits, and participants' rights (including the right to withdraw).
Community control. Communities decide what data is collected, how it is used, and what is made public.
Scenario planning. Ask: what is the worst-case scenario if this data is misused? If that scenario is unacceptable, do not collect the data or change your methods.

Risk assessment is not a one-time exercise. Revisit risks throughout the project as new information emerges or conditions change.

19.9 Community Review

Community review is non-negotiable. Research outputs must be reviewed by the community before publication or external use, not just for them. This principle flows from the community-first philosophy established in Chapter 1.4 and reinforced throughout this textbook.

Why community review matters:

Accuracy. Residents catch errors researchers miss. A map showing a park that has been closed for years, a service that no longer exists, or a boundary that does not match lived experience — these errors undermine credibility. Community review improves accuracy.

Interpretation. Data does not interpret itself. A map showing a cluster of services might look like abundance to an outsider but represent fragmentation and poor coordination to residents. Community members provide the interpretive context that data alone cannot.

Safety. Some findings, if made public, could cause harm. A map showing where undocumented immigrants access services could enable immigration enforcement. A map showing informal housing could trigger eviction. Communities decide what is safe to share.

Ownership. Communities own their stories and knowledge. Publishing findings without community consent is extractive. Community review is the mechanism through which communities exercise authority over research about them.

Trust. Researchers who skip community review — or treat it as a formality — damage trust. Future research in that community becomes harder. Researchers who take community review seriously build long-term relationships and open doors for future collaboration.

How to conduct community review:

Plan it from the beginning. Community review is not an afterthought. Budget time, resources, and logistics for at least two review sessions: one after preliminary findings, one before final publication.
Prepare accessible materials. Do not hand residents a 50-page academic draft full of jargon and expect useful feedback. Prepare summaries, maps, infographics, and presentations in plain language. Offer materials in multiple languages if needed.
Facilitate, do not present. Community review is not a one-way presentation. It is a dialogue. Ask open-ended questions: What surprises you? What is missing? What did we get wrong? What needs more explanation? What should not be shared publicly?
Compensate participants. People are giving their time and expertise. Provide honoraria, meals, or other compensation.
Document feedback. Take notes. Record (with consent) if helpful. Ensure feedback is integrated into revisions.
Revise based on feedback. If community members say a finding is inaccurate, misleading, or unsafe, take it seriously. Revise. If you disagree, discuss why — but the community has final say on what represents their lived experience.
Seek consent before publication. After revisions, confirm that community partners consent to publication. Some projects may require formal sign-off from community organizations or Indigenous governments.
Return findings in usable formats. Communities need findings they can use, not just academic papers. Provide maps, reports, presentations, and datasets in formats partners can access and share.

Community review is sometimes slow, sometimes uncomfortable, sometimes reveals that you got things wrong. That discomfort is the price of ethical research. Embrace it.

19.10 Research Outputs

Research outputs are the products of your inquiry: maps, reports, dashboards, presentations, datasets, stories. In Community Mapping, outputs must be designed for use, not just publication.

Maps. The most visible output. Maps must be accurate, accessible, and ethically framed. Design maps for the intended audience: a map for a municipal planning committee looks different from a map for a community workshop. Include legends, context, data sources, and dates. Acknowledge limitations.

Reports. Written summaries of findings, methods, and recommendations. Community reports should be concise (10-20 pages), visually engaging, and jargon-free. Academic reports may be longer and more technical but should still be accessible to non-specialists. Always include an executive summary and plain-language summary.

Data dashboards. Interactive platforms where users can explore data, toggle layers, and generate custom views. Dashboards are powerful for ongoing monitoring and decision-making but require technical capacity to build and maintain. Ensure dashboards are accessible (screen-reader compatible, mobile-friendly).

Presentations. Oral presentations to community groups, decision-makers, or public audiences. Presentations should be visual, story-driven, and time-appropriate (15-30 minutes, not 90). Leave time for questions and dialogue.

Datasets. Raw or processed data made available for others to use. Open data supports transparency and secondary analysis but raises ethical concerns: who might misuse the data? What privacy protections are in place? Consult community partners before releasing datasets publicly.

Stories and multimedia. Photovoice exhibits, video documentaries, oral history archives, story maps. These outputs center community voice and lived experience. They are particularly powerful for public engagement and advocacy.

Policy briefs. Short (2-4 page) summaries designed for decision-makers. Policy briefs answer: What did you find? Why does it matter? What should we do? They are written in direct, actionable language with clear recommendations.

Academic publications. Peer-reviewed journal articles or book chapters. Academic outputs are important for knowledge dissemination and researcher career advancement, but they should not be the only or primary output. Community partners rarely benefit from paywalled journal articles. If you publish academically, also produce community-accessible outputs.

Outputs must be:

Accessible. Available in formats and languages that partners can use.
Actionable. Clear about what findings mean and what actions they support.
Attributed. Acknowledge community partners, co-researchers, and data sources.
Archived. Stored securely and accessibly for future reference.

Plan outputs early in the research design. Different outputs require different resources, skills, and timelines. A dashboard requires technical skills. A video requires filming and editing. A policy brief requires concise writing and political fluency. If you do not have the capacity to produce a planned output, revise your plan.

19.11 Synthesis and Implications

Research design is not glamorous. It is the scaffolding, not the building. But without strong scaffolding, the building collapses.

This chapter has walked through the essential components of designing rigorous, ethical Community Mapping research: asking the right question, defining scope, engaging stakeholders, selecting methods, building timelines, assessing risks, planning community review, and designing outputs. Each component is critical. Skip one, and the research is weaker. Shortcut ethics, and the research is harmful.

The implications extend beyond individual projects. Research design is also a statement of values. A research plan that includes community review, participant compensation, and accessible outputs signals respect for community authority. A research plan that treats community members as data sources, not co-researchers, signals extraction. Design choices reveal what you believe about power, knowledge, and whose voice matters.

For students and early-career researchers, learning to design research well is foundational. Research design is not taught in a single course or chapter — it is a skill refined through practice, feedback, and reflection. Use the Research Design Template (§19.12) as a starting scaffold, but do not treat it as a rigid formula. Adapt it to your context, your relationships, and your community partners' needs.

For experienced practitioners, research design is a discipline worth revisiting. It is easy to fall into routines, to reuse old templates, to skip steps when timelines are tight. Resist that drift. Community Mapping research deserves careful design every time.

Finally, remember that research design is iterative. You will not get it perfect on the first draft. You will learn as you go. Community partners will offer feedback. Data will surprise you. Timelines will shift. That is normal. The goal is not perfection — it is integrity, rigor, and accountability to the communities whose lives your research touches.

19.12 Research Design Template

This template provides a reusable structure for planning Community Mapping research. Adapt it to your project's needs. Fill it out collaboratively with community partners.

Research Question

State your primary research question. Be specific and answerable.

Example: Where do seniors without access to a car live relative to healthcare services, and what transportation barriers do they face?

Scope

Define the boundaries of your research.

Geographic area:

Time period:

Population(s):

Methods in scope:

Methods out of scope:

Key limitations or exclusions:

Community Definition

Who is "the community" for this research? How are you defining community boundaries (geographic, cultural, identity-based, interest-based)?

Community definition:

Who invited you or supports this research?

What relationships do you have in this community?

Stakeholders

List key stakeholders. Specify their role, interest, and power.

Stakeholder	Role	Interest (Low/Medium/High)	Power (Low/Medium/High)	Engagement strategy
Example: Residents of Neighborhood X	Primary participants	High	Low	Community workshops, focus groups
Example: Municipal Planning Dept	Funder, data source	Medium	High	Quarterly updates, final report

Methods

List the methods you will use. Specify sample size, timeline, and responsible party.

Method	Purpose	Sample/Target	Timeline	Responsible party
Example: Focus groups	Understand barriers to healthcare access	3 focus groups, 8-10 participants each	Weeks 4-6	Research team + community partner

Timeline

Break your project into phases. Identify key milestones.

Phase	Tasks	Timeline	Milestone
Example: Design	Finalize research plan, secure ethics approval	Weeks 1-4	Ethics approval received
Example: Data collection	Conduct focus groups, collect GIS data	Weeks 5-10	All focus groups completed

Resources

List required resources and how they will be secured.

Funding:

Staff/volunteers:

Technology/tools:

Space:

Participant compensation:

Other:

Risk Register

Identify potential risks and mitigation strategies.

Risk	Likelihood (Low/Medium/High)	Impact (Low/Medium/High)	Mitigation strategy
Example: Low focus group recruitment	Medium	High	Partner with trusted community organization for recruitment; offer flexible times; provide honoraria

Community Review Plan

How will you ensure community review of findings?

Review round 1 (preliminary findings):

When:
Format (workshop, presentation, written materials):
Participants:

Review round 2 (final findings before publication):

When:
Format:
Participants:

Consent process for publication:

Research Outputs

List planned outputs. Specify format, audience, and timeline.

Output	Format	Audience	Timeline
Example: Community report	15-page PDF, plain language	Residents, community organizations	Week 18
Example: Policy brief	3-page brief with maps	Municipal decision-makers	Week 20

Ethics and Consent

Specify how you will address ethics and consent.

Ethics review required? (Yes/No):

Ethics board/process:

Consent procedures:

Data security measures:

Special considerations (e.g., Indigenous protocols, vulnerable populations):

Key Takeaways

Research design is the structured plan that connects questions to methods, methods to data, and data to conclusions in Community Mapping projects.
The right research question is clear, answerable, important to the community, and ethical to pursue.
Scope must be defined explicitly: geographic area, time period, populations, methods, and resources.
Stakeholder identification is essential but distinct from power mapping; engagement strategies must match stakeholder interest and influence.
Method selection flows from research questions and must balance rigor, accessibility, community voice, and capacity.
Community review is non-negotiable — research outputs must be validated, interpreted, and consented to by the community before publication.

Plain-Language Summary

Research design is the plan for how you will do Community Mapping research. It's like a blueprint: it shows what you're going to do, why, when, and with whom.

Good research design starts with a clear question that matters to the community. It defines boundaries — what you'll map and what you won't. It identifies who should be involved and what methods you'll use. It includes realistic timelines, resources, and plans for dealing with risks.

Most importantly, good research design includes community review. That means sharing your findings with the people you mapped and getting their feedback before you publish anything. They'll catch mistakes, add context, and help you understand what your data actually means. They also decide what's safe to share publicly and what's not.

Research design isn't glamorous, but it's essential. A good plan leads to good research. A weak plan leads to wasted time, broken trust, and findings that don't help anyone.

End of Chapter 19.

Chapter 19. Community Mapping Research Design