Open Decisions

Decisions that need to be resolved before the CoE launches. Updated as items are resolved.

1. Cohort roster

Status: Two core owners confirmed (Kate, Mary). Three more in conversation. Three seats still open. Owner: Alex + Mike Details: See Roster Planning for the current map of who’s in conversation and what seats are still open. The cohort is forming around the full product-data cascade: creation → finalization → PIM entry → PO consumption → downstream data quality. Next step: Conversations continue with people in the “in conversation” list. Three seats (Product Development, Inventory Planning, Tree Merchandising) are still open — any Balsam teammate whose day-to-day fits those descriptions is welcome to reach out.

2. Slack and comms setup

Status: Not started. Owner: Mike + Alex Details: Each cohort needs a communication channel. Decisions:

  • Slack channel per cohort? Naming convention?
  • Async norms — response time expectations, what goes in Slack vs. GitHub
  • How operators (Mike, Alex) stay available through the day
  • How adjacent ring members get visibility without noise

3. Data access

Status: Not started. Owner: France (CTO) Details: What data access does the cohort need and who grants it? Kate and Mary already have access to PIFs, PIM, and some downstream systems. Other cohort members may need:

  • Snowflake / Sigma access for product data views
  • PIF file access (currently in Excel/SharePoint)
  • ContentServ/Centric PIM access
  • Spatial Edge platform access (once available) Next step: Scope access needs before the cycle starts. Surface blockers in first sponsor sync, not halfway through.

4. Cohort GitHub repo

Status: Not started. Owner: Mike + France Details: The cohort needs a GitHub repo on Balsam’s org (not Goose Group). Decisions:

  • Which GitHub org? Does Balsam have one? If not, create it.
  • Repo name and structure (use the TEMPLATE from this repo as scaffold?)
  • Who has access? Cohort members + operators + sponsors
  • How does the microsite read from it? (GitHub Actions, API at build time, or manual sync)

5. In-person launch logistics

Status: Pending — Claire said week after offsite works better. Owner: Claire + Alex Details: Claire (Apr 17): “I would say the next week would work better, but we’ll need to see what location (Boise, ID v RWC, CA) makes sense depending on participants.” Depends on:

  • Cohort roster (who’s where)
  • Kate and Mary’s location and travel
  • Alex’s availability (currently in the Americas) Next step: Finalize roster first, then coordinate locations with Claire.

6. Spatial Edge engagement model

Status: Call happened Apr 16. Details pending. Owner: Mike + Alex + France Details: SE will build a data platform making product data accessible. Open questions:

  • How does SE’s work connect to the cohort’s work? Timeline alignment?
  • Does the cohort need SE platform access during the sprint?
  • What does “hacker” mean in the cohort if SE handles engineering?
  • Who coordinates between the cohort and SE? Reference: Spatial Edge transcripts in GG Swerk (project: product-data-pipeline).