In partnership with TechSoup and The Ballmer Group The Data and Technology Hub equips communities to measure and multiply their impact. Where a child grows up in the U.S. too often determines their access to education, jobs, housing, and economic opportunity. Cradle‑to‑career place‑based partnerships are doing the hard work of building pathways to economic mobility — but many lack the data, tools, and technical capacity needed to understand what works and scale it. We exist to change that.
The CEO of Data and Technology Hub is a founder building a national organization from scratch. She is the primary fundraiser, the most visible relationship holder, and the person every external stakeholder wants to reach. Your job is not to manage her calendar — it is to manage her capacity. You are a strategic gatekeeper, a force multiplier, and the person who ensures the CEO is always prepared, never blindsided, and focused on the highest-leverage use of her time. It is Monday, 7:45am. The CEO flew out at 6:00am for a two-day site visit in Washington, D.C. with the Robert and Tara Smith Foundation — Data and Technology Hub’s largest funder and the relationship the organization depends on most. She lands at 1:00pm, has a 2:30pm check-in with the program officer, a 5:00pm dinner with a prospective partner, and a full Tuesday of foundation meetings. She is unreachable until 1:00 pm. By 9:00am, four things have landed on your desk. Situation 1 — A calendar decision you cannot delay A board member of the Robert and Tara Smith Foundation has emailed asking if the CEO can meet her for a 30-minute coffee today at 1:30pm — between the CEO’s arrival and her 2:30pm program officer meeting. The CEO has been trying to build this relationship for months; the two have never met in person. The problem: 1:00–2:30pm was designed as the CEO’s prep window before the most consequential meeting of the quarter. The foundation board member needs a response by 10:30am. You cannot reach the CEO. Situation 2 — A funder request with a data problem inside it The Robert and Tara Smith Foundation program officer’s assistant has emailed asking for a one-page organizational snapshot to include in the program officer’s briefing file — due by end of day. You know from last week’s team meeting that Data and Technology Hub’s Q3 partner metrics are still being reconciled: two partner organizations submitted corrections late, and the numbers in the CEO’s deck have not been updated. No final version has been approved. Situation 3 — An email the CEO has not seen, from someone she should not keep waiting A message arrived Friday afternoon from the executive director of Northside Cradle-to-Career — a key partner organization that has been quietly frustrated by a missed delivery last quarter. The message reads: “Hi — wanted to connect before the end of the week. I have a few things I’d love to discuss directly with \[CEO name], when she has a moment.” The CEO does not know this email exists. It is now three days old. Situation 4 — An internal judgment call The Senior Director of Operations messages you: “Heads up — the fiscal sponsor flagged another vendor payment this morning. I think I can handle it without looping in the CEO, but wanted to check with you first since she’s traveling. What do you think?” Situation 5 — Anticipating what the CEO doesn’t know she needs Beyond the four issues above, you have 90 minutes before the CEO lands. You know her week: tomorrow is a full day of the Robert and Tara Smith Foundation meetings, Wednesday she has three back-to-back internal calls, Thursday is a board prep session, and Friday she is presenting to a prospective funder she has never met. What do you do with those 90 minutes to set up her entire week — not just today? Think about: what does she need prepared that she hasn’t asked for? What is likely to go wrong this week that you can get ahead of? What context or materials should be waiting for her when she opens her laptop on the plane home tomorrow night? What to produce: 1\. Written Document — One document, four clearly labeled parts: Write out your decisions for Situations 1 and 2. For the calendar conflict: state your call and draft the exact message you would send to the foundation board member. For the funder snapshot request: explain what you would send, what you would not send, and why — and how you would communicate the situation to the program officer’s assistant. Draft a response to Situation 3 on the CEO’s behalf — written in her voice, warm but not over-apologetic. Then write two sentences explaining how you would handle Situation 4 and what principle guides your answer. For Situation 5: write a short “Week Ahead” brief (half-page max) that you would have ready for the CEO by the time she lands. This should cover: what’s coming, what’s been prepared, what decisions she’ll need to make, and anything you flagged or handled proactively. This is your chance to show how you think ahead, not just react. Draft a one-page briefing note to prepare the CEO for her 2:30pm meeting with the Robert and Tara Smith Foundation program officer. Include: the key relationship context, what the CEO should be ready to address, and any open items or risks she should know walking in. Video Walkthrough — 5 to 7 minutes: Record a 5–7 minute video walking through your decisions and the briefing materials. Talk through your prioritization logic, where you exercised judgment without being able to ask first, how you set up the CEO’s week proactively, and what AI or automation tools you would use in this role to stay ahead of the work (e.g., AI-assisted briefing prep, automated calendar intelligence, email triage and drafting, or meeting prep workflows).
It is day 45 at Data and Technology Hub. You are the new Senior Director of Operations. The CEO has been running everything herself — there are no documented processes, no operating cadence, and no shared source of truth for decisions, budgets, or project status. Five things need your attention right now: Funder scorecard: The primary funder has a quarterly review in 60 days. They expect a scorecard, a budget-vs-actuals update, and a progress narrative. Nothing is currently instrumented. Vendor approval process: The fiscal sponsor's finance team has flagged three vendor payments that went through without an approval workflow. They need a documented process within two weeks or they will pause all new vendor onboarding. Consulting engagements: Three active consulting engagements with community organizations have no intake documentation, no scoping agreements, and no record of what was promised. Executive Assistant onboarding: The Executive Assistant starts in three weeks with no onboarding plan, no systems access list, and no documentation of what the CEO needs supported. Success scorecard: The CEO has asked you to design the organization's success scorecard — but there is no agreed definition of success yet. Data and Technology Hub is building an AI-first operating model. The CEO does not want a traditional nonprofit back office she wants an operating system that is lean, automated where possible, and designed for a five-person team that punches above its weight. She expects you to identify where agentic AI workflows (automated approvals, intelligent document generation, AI-assisted reporting, meeting intelligence, workflow orchestration) can replace manual overhead — and where human judgment must remain. What to produce: Document 1: A one-page 30-day operating plan covering how you sequence these five issues, what you tackle in week one, and what you defer and why. Include a specific AI/agentic operations stack recommendation — name at least two tools or workflow automations you would implement first, explain what manual process each one replaces, and why you chose them over alternatives. Be specific about the workflow change, not just the tool name. Document 2: A short note (two paragraphs) to the fiscal sponsor's finance team about the vendor approval issue. Acknowledge the gap, propose a specific process, and set a realistic timeline. Video: A 6–8 minute video walking the CEO through your plan as a strategic partner — your prioritization logic, what you are protecting her from, where you need her input versus what you will own, and how your AI-first operations approach will give this small team structural leverage.
