Perform project management

I'm a senior fundraiser who needs a crisp definition of 'perform project management' for fundraising campaigns that separates it from 'program management' and 'operations management.' Using the PMBOK Process Groups framework by name, define project management in 60–80 words, state one concrete boundary where people commonly conflate the roles (with numbers/outputs), and give one rule I can paste into our team charter to keep the distinction clear.

Map 'perform project management' for fundraisers across mastery levels 1–5. Use the Work Breakdown Structure (WBS), Critical Path Method (CPM), and Stakeholder Analysis/RACI by name. For each level give 3 observable behaviors, one artifact they produce, and one blind spot they typically have.

Explain from first principles why a fundraising project manager's use of a Work Breakdown Structure (WBS) improves campaign outcomes. Reduce the argument to psychology and decision science mechanisms (e.g., cognitive load, goal-gradient, commitment devices) and cite relevant, widely-accepted research traditions (no obscure papers). End with two concrete heuristics a fundraiser can apply tomorrow when building a WBS.

Describe an anti-pattern: a fundraiser who believes they're excellent at performing project management but regularly derails campaigns. Using the Work Breakdown Structure (WBS) and Risk Management (Identify-Assess-Respond-Monitor) frameworks by name, list 6 concrete tells (behaviors, artifacts, metrics) that expose the gap between confidence and competence.

Roleplay: you're our impatient Executive Director playing the counterpart. I'm the lead fundraiser running a 6-month major-gifts campaign with a $1.2M target, constrained team of 3 FTEs, and a single shared prospect research resource (50% allocation). Use Critical Chain Project Management (CCPM) and Agile/Scrum by name to push back. I will propose a plan; play hardball and then critique my answer against CCPM and Scrum. Start by asking one blunt question that surfaces my biggest hidden assumption.

Walk me through a short, realistic failure autopsy where lack of project management caused a fundraiser-led campaign to miss a $900k milestone and lose two major donor prospects. Use PMBOK Process Groups and Risk Management by name. Outline the timeline (6–8 items with dates or weeks), the earliest two warning signs, and the one decision point where a different PM approach would have most likely prevented the loss.

I'm leading fundraising project management for a new $5M donor campaign. Explain how using Agile/Scrum to run fundraising work differs across (a) a 50-person nonprofit headquarters, (b) a 12-person startup charity, and (c) a fully remote, async global donor relations team. Use 'Work Breakdown Structure (WBS)' and 'Agile / Scrum' in your answer and give one practical change to our sprint routine for each context.

I run a 6-person fundraising team preparing our annual major-gifts campaign. Below is a draft Slack message I wrote to the team to kick off the planning sprint. Rewrite it to demonstrate strong use of the PMBOK Process Groups and a clear RACI for next two weeks—make it crisp, task-oriented, and motivational for fundraisers who hate bureaucracy. Draft: "Hey team — campaign planning meeting Thursday. Need ideas on target donors, outreach language, and timeline. Also figure out who will do outreach. Bring your notes."

I'm leading donor engagement across two regions: Region A (high-context, relationship-driven) and Region B (low-context, task-driven). Using the PMBOK Stakeholder Analysis/RACI and Agile communication practices, explain three concrete ways misunderstandings about timelines, meeting norms, and authority could derail our joint stewardship process—and give one practical script to resolve each misunderstanding.

Take the famous fundraising failure of the Red Cross during a prior disaster relief campaign (assume donor confusion and missed reporting deadlines hurt trust). Using PMBOK Risk Management and Critical Chain (CCPM) thinking, argue specifically how disciplined risk identification and protecting critical-chain buffers could have prevented the loss of donor trust. Make concrete recommendations fundraisers could add to their next campaign plan.

Last Thursday I led a 30-minute donor strategy sync where the new program manager pushed to delay a $120k ask until Q1 for a better prospect profile. I argued we should run a smaller $40k pilot this quarter to keep momentum. Using the PMBOK Process Groups and Risk Management (Identify-Assess-Respond-Monitor), coach me how my response should have been framed — include exact sentences to say, what documents/outputs to produce on the spot, and one immediate risk-response I should have proposed.

Help me map what 'project planning' looks like for a fundraiser at three levels: junior (1 year experience), senior fundraiser, and program manager. Use Work Breakdown Structure (WBS) and Critical Chain (CCPM) thinking to list 6 concrete artifacts or behaviors per level, with one real-world signal that shows someone has upgraded from junior→senior and another signal for senior→manager.

Simulate a 6-turn disagreement between our Director of Development (prefers PMBOK's formal approvals and gating) and our Head of Major Gifts (prefers Agile/Scrum rapid outreach) about whether to require a formal sign-off before launching a donor pilot. Both are experienced and persuasive but reach opposite conclusions. Make their arguments concrete (schedules, acceptance criteria, stakeholder lists), then ask me which side I back and press me to justify one trade-off I can't avoid.

I'm a senior fundraiser managing a 6-month capital campaign with a $3M target and a tight donor-research backlog. Use the PMBOK Process Groups and Critical Chain Project Management (CCPM) explicitly: when does too much planning (over-optimizing the Planning process group) become harmful for this campaign, and what does it trade off against (e.g., buffer protection, donor engagement velocity, risk exposure)? Produce a single concrete decision I can take today that accepts one specific trade-off and why.

I interview fundraiser project managers for a 45-minute slot. I want to assess their project risk management skill without asking 'are you good at risk management?'. Using the Risk Management (Identify-Assess-Respond-Monitor) framework, give me a 45-minute interview script: sequence of questions and a short scoring rubric that reveals their real ability to spot, prioritize, and respond to risks in a donor campaign.

Assess my capacity to perform fundraising project management. Ask me 10 questions, one at a time, that probe my use of PMBOK Process Groups, WBS, Critical Path/CCPM, stakeholder RACI, and Risk Management. After each of my answers, follow up once to press for a specific example or numbers. At the end, give a candid five-line readout of my level and one targeted development task.

I want one 5-minute daily practice that builds my fundraising project management skill (not generic time management). Use the Critical Path Method (CPM) and Risk Management framing: give a short ritual I can do at the start of each day, explain the mechanism (how it trains CPM and risk thinking), and what precise artifact I should update (one line).

Argue that strict use of Critical Path Method (CPM) and heavy upfront scheduling is overrated for a small fundraising team doing relationship-based donor cultivation. Then rebut yourself using PMBOK Process Groups, Agile planning, and Critical Chain arguments. End by stating where the truth likely sits for a 6-person team with fortnightly asks.

Design a 30-minute workshop to teach 'risk-aware fundraising project planning' to five fundraisers. Use the Risk Management (Identify-Assess-Respond-Monitor) framework. Include a 12-minute hands-on exercise, one discussion question that surfaces tacit judgment, and two take-home artifacts participants should leave with.

After any donor meeting, I want five post-meeting questions to evaluate how well I applied 'project monitoring & controlling' (PMBOK Process Groups + Risk Management). Each question should be actionable, include the artifact I should check, and a quick scoring rule (pass/fail or 0–2).