May 20th, 2026

Google doc notes (manually taken)

By next meeting, the goal is next week to have updated projects/initiatives in a trackable manner with issues

Anuar UstayevDaniela PopovaYoana PopovaMonika Popova UPDATE YOUR PROJECTS before the next weekly meeting
- Reflect: is there anything you are working on that doesn’t belong to any of the existing projects atm..
  - If yes, create a new project for it
  - If no, move forward
- For every active project, we want to be very explicit about what we are promising
- What exactly are we promising?
- By what date will that promise be judged?
- Plan of work
  - Milestone / checkpoint
  - ETA
  - Expected outcome / key result
  - Status (checkbox)
  - Completion date
- What is the one active issue tracking this work?
  - Understand where we are in the plan of work and with our promises
  - Every project MUST have at least one active issue in the leadlinks repo open (that is up-to-date) linked from the project page.
Yoana
- Promise: Establishing a rhythm of making sure everyone is executing their anchor moment = setting a process
- Each month we have focus point
- Add github issue to each project
Content engine - fix it

Need explicit promises and delivery dates for all projects
- Current markdown files insufficient for tracking progress
- Must create active GitHub issues for each project
- Cover pages should clearly show: project purpose, current status, next steps, completion criteria
Template updates coming with additional required fields
Goal: easy understanding of project status and timeline by next meeting

Establishing monthly process for all Datopian products
- Beginning: planning meeting/sync for anchor moment agreement
- Middle: progress check
- End: review and execution verification
April cycle failed - no teams executed anchors
May anchors agreed but execution tracking unclear
- Porto JS on track with civic data portal focus
- Data Hub and Flowershow agreements in place, progress untracked
Challenge: need systematic way to verify anchor moment completion
- Product owners must confirm execution monthly
- Table tracking system planned but missing from current page

Social Media Posting
- Currently covers Datopian and Porto JS content
- Adding CKAN due to business importance
- Separate from individual product marketing (Data Hub, Flowershow have own projects)
Newsletter Launch
- Blocked on framing multiple products cohesively
- Solution: Welcome issue for May (20th CKAN anniversary)
  - Simple “we’re back” message
  - Outline future newsletter content
  - Avoid complex product integration in first issue
Content Engine Initiative needs restructuring
- Should encompass all content production
- Include social media, blog posts, Datopian website content

Tool evaluation complete but scope unclear
Rufus feedback revealed missing requirements from other team members
Current solution (Notion) works for Monika’s sales process
Need team-wide jobs-to-be-done analysis
- Each team member must define CRM requirements
- Tool should support easy onboarding of future salespeople
- Consider process enhancement opportunities beyond current workflows