This is not a survey. It is a design conversation. Your answers shape what gets built for Phase 2 — the features we prioritize, the way the weekly synthesis call runs, and what the Field Log looks like for your team through October.
Take 15 to 20 minutes. Answer what you can. Leave the rest for our conversation. There are no wrong answers here.
This document was shaped by the change maps your team completed and the huddles Kord has been welcomed into. Your candor so far has made everything better. This is the next step in that same conversation.
Start here
Who are you?
Your name helps Kord read your responses in context. John and Robert's answers will be reviewed together but kept separate for discussion.
What do you most want to know coming into the weekly call?
Select everything that matters to you. We will design the call format around your answers.
Cohort energy levels
Who has and has not logged
Themes across entries
Friction points by department
Outliers needing immediate attention
Comparison to prior weeks
Individual analyst flags
What format works best for Robert in a 30-minute call?
Think about how Robert actually prepares for meetings and what helps him engage most effectively.
Brief written summary in advance
Live verbal synthesis, no pre-read
Combination of both
A one-page dashboard to review async
Are there departments or situations you want flagged immediately — not waiting for the weekly call?
Think about the situations where a week's delay would matter.
Who else should be on the weekly call?
John and Kord only
John, Robert, and Kord
Add Jojo as Senior MA lead
Rotating cohort member
TruGov POC
02Facilitator and observer views▼
Robert expressed interest in visibility into cohort health without his own entries affecting the synthesis. What does that visibility need to show him?
Robert sees the program as a sponsor, not a participant. Design his view around that role.
One-page weekly dashboard
Traffic light by analyst
Narrative summary
Raw entry access
Energy level trends over time
Department-level friction map
John needs a view that helps him manage the program week to week. What does useful look like for him?
Who has logged and when
Energy level trends over time
Individual analyst flags
Department-level friction map
Comparison to prior weeks
AI synthesis before each call
When John or Robert leaves a note on the facilitator view, should the relevant analyst see it?
This is a meaningful design decision. Private notes give leaders candid space. Visible notes could create accountability or feel intrusive.
Private — only John and Robert see notes
Visible — analyst sees the note
Depends on the note
Should there be a way to send a message to the full cohort through the Field Log?
For example: a weekly acknowledgment of something the synthesis surfaced, or a prompt adjustment mid-week.
Yes — cohort-wide messages would be useful
No — keep communication outside the tool
Maybe — depends on the situation
03Participant experience▼
What would make you log every week if you were a participant? What would make you stop?
Be honest. The habit is the hardest part. What actually works for this team?
Are there additional prompts specific to the Anaplan implementation that would make entries more useful?
Current prompts: what did I try, what happened, what would I do differently. These are intentionally broad. Should we add anything more specific?
How did your department contact respond this week
Where is your department on the ADKAR scale
What would you tell next week's you
Keep it broad — no Anaplan-specific prompts
Should the Field Log show analysts a weekly plus/delta from the synthesis — what's working across the cohort, what the group would change?
This creates transparency but could also create unintended dynamics. Worth thinking through carefully.
Yes — shared visibility would help the cohort
No — keep synthesis in the facilitator view only
Show a summary but not individual entries
Is there a moment in the week when logging makes the most sense for this team?
Right after a department interaction
End of day Friday
Monday morning — reflection on prior week
No set time — whenever it fits
04The closing reflective session▼
What do you want the cohort to walk away from the closing session knowing about themselves that they did not know in June?
The closing session produces a written synthesis document — the institutional record of BPP 11. Who should receive it?
BPP team only
Robert and county leadership
GFOA submission support
Public-facing case study (with permission)
What format would make the closing session most meaningful for this team?
Facilitated reflection using Field Log entries
Structured retrospective with plus/delta
Cover Story revisited — did we get there
Individual and group commitments for next cycle
05The Field Log as a product▼
San Mateo County is the origin story for this product. Are you comfortable with BPP 11 being referenced as the pilot program in product materials?
No individual names or sensitive details would ever be disclosed. This would be at the program level only, and only with your explicit sign-off.
Yes — comfortable with that
Yes, but I'd want to review anything first
Not sure — let's discuss
No — prefer to keep this private
Is there any interest in San Mateo County having a formal role in the product's development beyond this engagement?
Advisory input on product direction
Case study rights and attribution
Early access to new features
Licensing arrangement for future county use
Not at this time
What would make this tool worth recommending to a colleague running a similar program in another jurisdiction?
06Anything else▼
Is there anything the Field Log should do that we have not asked about?
Questions you expected to see. Features you need. Concerns you have. Anything that belongs in this conversation.
Ready to submit?
Your responses go directly to Kord. He'll review them before your next conversation and build Phase 2 around what you've shared here. No formal follow-up required — your answers are enough to get started.
Thank you. Your responses have been recorded. Kord will review them before your next conversation. If you want to add anything, reach out to him directly.