Senior Director of Measurement & Impact (Volunteer)

We need to produce HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We need to extract relevant content from the posting. The posting is about Senior Director of Measurement & Impact (Volunteer). It includes description of organization, role overview, responsibilities (many bullet-like paragraphs). No explicit "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule" sections. There is mention of commitment: Approximately 5–10 hours per week, Minimum Commitment 6 months. That's schedule/commitment info. Could be placed under Schedule section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Schedule if we have info. Also maybe Benefits? Not mentioned. Pay? Not mentioned (volunteer). Requirements/Qualifications/Skills not explicit; but we could infer from responsibilities but we must not invent. So we should not create those sections if no explicit content. Thus we will have sections: About the role (maybe role overview), Responsibilities (list of duties), Schedule (commitment). Possibly also "About Mentor A Promise" but that's organization description; could be part of About the role? The instruction: About the role heading for section headings. Could include overview of role and organization. We'll put About the role containing description of MAP and PromiseMeasure and role overview. Responsibilities: we need to extract bullet-like duties from the role overview and subsequent sections: Measurement & Impact Leadership, Theory of Change & Outcomes Frameworks, Monitoring & Evaluation, Data & Measurement Systems, Data Quality & Integrity, KPIs & Performance Measurement, Surveys, Assessments & Feedback, Youth & Family-Centered Measurement, Impact Analytics & Reporting, Evidence & Claims Review, Continuous Improvement & Organizational Learning, Cross-Divisional Measurement Partnership. We'll turn each bullet into

items under a

. Ensure we preserve all substantive information, not summarizing away detail. That's a lot; we need to include all points but can combine similar? Must not invent or summarize away detail. We can list each responsibility as separate
• with the text from the posting. Might be lengthy but okay. We must not include boilerplate like EEO etc. The posting didn't have that. We need to avoid repeating job title as heading. We'll not include that. We'll output only HTML fragment. Let's craft:

  About the role

  Mentor A Promise (MAP) is a New York City–based nonprofit serving children and youth (ages 5–18) experiencing housing instability... [description] ... The Senior Director of Measurement & Impact serves as the second-in-command of PromiseMeasure and the principal execution leader beneath the Chief of Measurement, Evaluation & Impact. ... Commitment Approximately 5–10 hours per week, Minimum Commitment 6 months. Reports To Chief of Measurement, Evaluation & Impact. Directly Oversees PromiseMeasure Department Directors, Managers, Leads, Analysts, Specialists, and designated measurement initiatives. Works Closely With ... list of divisions.

  But we need to keep schedule separate? Could include schedule in About the role but better to have Schedule section. We'll put schedule info in Schedule section:

  Schedule

  • Approximately 5–10 hours per week
  • Minimum commitment of 6 months
  Now About the role: include organization description and role overview but not schedule details. Responsibilities: we need to list each duty. Let's extract from the text: From "Measurement & Impact Leadership": - Translate the Chief's measurement and impact strategy into implementation plans, priorities, milestones, and deliverables. - Lead day-to-day execution across PromiseMeasure. - Establish consistent organization-wide measurement practices. - Develop practical frameworks for measuring outputs, outcomes, performance, quality, experience, and longer-term impact. - Establish measurement expectations appropriate to different MAP programs and initiatives. - Ensure measurement efforts remain proportional to the decisions they are intended to inform. - Identify gaps in MAP's ability to understand organizational performance and impact. - Recommend improvements to the Chief and appropriate organizational leaders. - Not everything that matters can be reduced to a number. Not every number that can be collected is worth collecting. PromiseMeasure should know the difference. (This is more a statement; maybe include as a responsibility? It's a principle; we could include as a bullet but it's not an action. Might be okay to include as a responsibility: "Recognize that not everything that matters can be reduced to a number and not every number that can be collected is worth collecting." But it's more a statement. We'll include as a bullet maybe. From "Theory of Change & Outcomes Frameworks": - Help MAP establish clear connections among Need → Activities → Outputs → Short-Term Outcomes → Intermediate Outcomes → Long-Term Impact. - Work with divisions to clarify intended outcomes. - Develop theories of change and logic models where appropriate. - Identify assumptions underlying programs. - Define indicators. - Establish baselines where feasible. - Determine reasonable targets or benchmarks. - Identify appropriate data sources. - Establish measurement frequency. - Clarify responsibility for collection and reporting. - Determine how findings will inform decisions. - A measurement framework should begin with understanding what MAP is trying to accomplish—not with deciding what fields can fit into a spreadsheet. (again principle) From "Monitoring & Evaluation": - Oversee monitoring and evaluation approaches across MAP programs and initiatives. - Develop evaluation plans appropriate to program maturity and organizational capacity. - Support formative, process, implementation, outcome, and other appropriate evaluation approaches. - Establish evaluation questions. - Develop indicators and measurement plans. - Review data-collection methods. - Assess implementation fidelity where appropriate. - Analyze program performance and outcomes. - Identify patterns and differences among participant experiences where the data responsibly permits. - Communicate limitations and uncertainty. - Translate findings into practical recommendations. - Evaluation should help MAP improve programs—not simply produce reports about them. From "Data & Measurement Systems": - Strengthen the infrastructure through which MAP collects, organizes, validates, analyzes, and uses measurement data. - Responsibilities may include: - Data dictionaries - Indicator definitions - Data-collection protocols - Measurement calendars - Data-validation procedures - Data-quality checks - Documentation standards - Dataset organization - Reporting workflows - Dashboard requirements - Measurement repositories - Version control - Data lineage and source documentation where appropriate - Partner with PromiseStack on technical infrastructure and PromiseShield on privacy, data protection, access, and appropriate information-handling requirements. - The goal is to create data people can trust. From "Data Quality & Integrity": - Establish clear expectations for measurement quality. - Monitor dimensions such as Completeness, Accuracy, Consistency, Timeliness, Validity, Reliability, Documentation, Appropriate interpretation. - Develop processes for identifying and resolving data-quality issues. - When data is incomplete, uncertain, or methodologically limited, say so. - MAP should never make a stronger claim than its evidence can responsibly support. From "KPIs & Performance Measurement": - Lead the development of meaningful organizational and program-level key performance indicators. - Help leaders distinguish among Activities → Outputs → Quality → Outcomes → Impact. - For example, the number of workshops delivered may describe activity. Attendance may describe reach. Participant experience may describe quality. Demonstrated development may indicate an outcome. Those measures answer different questions and should not be treated as interchangeable. - Develop performance systems that help leadership understand what is on track, what requires attention, and what decisions may be necessary. From "Surveys, Assessments & Feedback": - Oversee the development and appropriate use of measurement instruments involving Students, Parents and caregivers, Mentors, Volunteers, Educators, Partners, Program participants, Staff and organizational stakeholders, where appropriate. - Strengthen Survey design, Question construction, Response scales, Administration methods, Accessibility, Timing, Response-rate strategies, Analysis, Documentation, Interpretation. - Avoid collecting information simply because it might be interesting someday. - Every meaningful question should have a reason for being asked. From "Youth & Family-Centered Measurement": - Ensure measurement involving young people and families reflects MAP's dignity-centered and safeguarding commitments. - Use age-appropriate instruments. - Minimize unnecessary data collection. - Avoid intrusive questions without legitimate purpose. - Consider accessibility and language needs. - Protect confidentiality. - Establish appropriate consent and permission processes where required. - Avoid repeatedly asking participants to recount difficult experiences merely to demonstrate organizational impact. - Explain how information will be used where appropriate. - Create opportunities for participants to understand what MAP learned from their feedback. - People are not data points. Measurement should help MAP understand experiences without reducing individuals to the information collected about them. From "Impact Analytics & Reporting": - Oversee the development of Executive dashboards, Program dashboards, Impact reports, Evaluation reports, Measurement summaries, Outcome reports, Data visualizations, Leadership briefings, Board-ready measurement materials, Grant and partnership impact information, Organizational performance summaries. - Translate technical findings into clear language without sacrificing accuracy. - Senior leaders should be able to understand: What does the evidence show? How confident are we? What does it not show? Why does it matter? What should we consider doing next? From "Evidence & Claims Review": - Help protect MAP's credibility by establishing standards for organizational impact claims. - When MAP communicates results externally, PromiseMeasure should help verify that claims are supported by available evidence. - Partner with PromiseGiving, PromiseBridge, PromisePublic, PromiseVoice, and Executive Leadership when measurement information is used for grants, fundraising, partnerships, reports, advocacy, presentations, or public communications. - PromiseMeasure should never become the department asked to find a number that makes an already-written claim sound convincing. - Evidence should inform the story. The story should not determine the evidence. From "Continuous Improvement & Organizational Learning": - Build feedback loops that connect measurement to action. - Use a cycle such as Measure → Understand → Discuss → Decide → Improve → Reassess. - Facilitate conversations about: What is working, What is not, What surprised us, What changed, What remains unclear, What participants are telling us, What needs further investigation, What should be improved, What should continue, What should stop. - Measurement becomes valuable when learning changes behavior. From "Cross-Divisional Measurement Partnership": - PromiseMeasure should function as an internal measurement partner rather than a distant auditing function. - The Senior Director will help divisions define appropriate outcomes, indicators, data needs, and evaluation approaches while respecting functional ownership. - PromisePrograms owns program delivery. PromiseLearning owns educational quality and learning design. PromiseRise owns career-readiness and youth-pathway programming. PromiseFinance owns financial acc (cut off). We'll include what we have. We need to ensure we don't include incomplete sentence at end: "PromiseFinance owns financial acc". That's truncated; we should not include incomplete info. We'll stop before that. Now we need to format as
  • for each responsibility. That's many items; okay. We must not include headings for sections lacking content: Requirements, Qualifications, Skills, Benefits, Pay. We'll output:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Schedule

    • Approximately 5–10 hours per week
    • Minimum commitment of 6 months
    Make sure no extra markdown. Let's craft About the role paragraph: combine organization description and role overview. Organization description: "Mentor A Promise is a New York City–based nonprofit serving children and youth (ages 5–18) experiencing housing instability, grounded in the belief that every child is a Promise—full of potential, dignity, and possibility. We deliver consistent, high-quality programming across mentorship, literacy, social-emotional learning, and creative expression in shelters, schools, and community spaces, creating structured environments where students