Strategy Meeting
Artifact info
Title:

Holomovement Next Phase Planning & Domain Prioritization

Engagement:

Iris Internal

Client:

Iris Cocreative

Meeting Date:
June 16, 2026
Next Meeting Date:
No items found.
People
James Redenbaugh
Sean Grahm
Artifact Image
Meeting Summary

Reconnection & Project Status

After James returned from his honeymoon in the Azores, the team reconnected to assess project momentum and map out priorities for Hollow Movement's next phase. Sean shared that recent projects wrapped up smoothly during James's absence, including Uncommon Partners and Re Village, with Matt potentially reaching out for additional features. Sean also supported Wendy's project (Mailchimp newsletter setup, content updates) and collaborated with Ashley on ClickUp organization (08:16).

The Webflow [tag="webflow"] marketing sites have required minimal maintenance, leaving capacity for deeper Hollow Movement work as the post-launch wave settles (10:39).

🎯 Strategic Vision for Hollow Movement Next Phase

With the launch wave complete, James plans to zoom out and repropose the next phase to the Hollow Movement team. The client relationship is unusually open — they trust IRIS Cocreative [tag="iris"] to drive direction without rigid KPIs or fixed timelines, which has allowed the platform's true value to reveal itself organically: the people, the Holons, and the connections between them (54:41).

James framed the strategic question going forward: "How do we design this to be in service to that? How do we get out of the way of the people finding each other and building?"

🏗️ High-Level Domains for Next Phase

James outlined the major domains that will structure upcoming work:

Online Learning Platform

Building an LMS into Hollow Movement is a major undertaking. James has designed a clean LMS interface that can be ported into Webflow [tag="webflow"] components, integrated with the existing Supabase [tag="supabase"] backend (12:36). Some course/lesson/topic infrastructure already exists in Supabase, but a full strategy session is needed to scope what's there versus what needs to be built.

[technology="Online Learning Platforms"]

Custom Code → Webflow Component Migration

Several elements are currently fully custom code (the surface on Holons, the Wave page, chat components). The team will progressively rebuild these using Webflow [tag="webflow"] elements so they can evolve alongside the rest of the site's design system. Sean will incrementally transform the design system style guide from a custom code page into proper Webflow components as he updates messaging and other features (35:20).

Resource Library

James wants the resource library to be more than a grid of posts — something node-based and dynamic, inspired by Obsidian, where connections between resources are visible (19:00). It should be searchable, agent-accessible, and viewable in multiple ways. This pattern will likely extend across IRIS projects, potentially connecting resource libraries across sites like Iris and Hollow Movement.

[technology="Community Facilitation Tools"]

Email Notification System

This week James will focus on building a robust email notification system using n8n [tag="n8n"] so members get notified about unread messages, Holon updates, and other activity. Currently only Holon email invitations exist. James will handle this himself given his familiarity with the existing infrastructure (21:15).

[technology="Communication Automations"]

App Version Exploration

The team is exploring how to turn Hollow Movement into a true app — primarily to enable push notifications, which is the missing piece for replacing tools like WhatsApp for groups. The app version would be a simplified subset focused on messaging and course content, while the platform itself remains desktop-first since it's designed for collaboration and meaningful work (23:22).

Navigation Redesign

James loves the current top navigation but suspects users aren't discovering features — analytics will confirm this. The team is considering a sidebar nav in addition to the top bar, possibly with dropdowns or a mega menu (17:46). Sean offered to lead this in Figma, drawing on his enterprise app design experience to consolidate the two navigation sections thoughtfully (56:29).

🗺️ Map UI Evolution

As user count grows (~300 members), the map needs evolution. Ideas explored:

  • Dots should scale relative to zoom level — small at high altitude, growing as users zoom in
  • Implement clustering so dense regions like the Northeast don't collapse into a single overlap
  • Add filters to view just people or just Holons (the line density will become unmanageable otherwise)
  • Create a component version of the map for individual Holon pages — e.g., a spherical globe hero on the "Emerging Consciousness" Holon showing members and their connections

[technology="Parametric Geometric Interfaces"]

🔒 Privacy & Analytics as Linked Domains

Privacy and analytics will be developed together as a coordinated strategy.

Cookie Consent & GDPR

The most urgent low-effort task: Sean will port the working cookie consent bar from the floors project into Hollow Movement. The previous solution used Finsweet, which discontinued free support (26:46).

Privacy-First Analytics

Sean recommended Microsoft Clarity for behavioral analytics (free, privacy-aware) once cookie consent is in place. James wants to avoid Google Analytics and is cautious about Microsoft — the team will co-develop a robust, innovative privacy policy with the Hollow Movement team that makes explicit which data is used where, with the most sensitive data (like message content) walled off most heavily (42:50).

Encrypted Data + Local Agent Architecture

James proposed a forward-looking architecture: sensitive data like messages could be encrypted such that not even James or Sean can read it, then analyzed by a designated agent running on a local machine that strips personal identifiers before generating insights. This would enable powerful aggregate insights (sentiment trends, conversation volumes, emerging themes) without compromising individual privacy (45:57).

🤖 The "Holos" Agent Vision

A central long-term vision emerged: Holos as a self-aware being. The platform would have multiple data inputs feeding sub-agents (some local, some cloud), with a general awareness layer connecting them. This agent would have context on:

  • User profiles and Holons
  • The resource library
  • Online learning content
  • Publicly available external info (scraped websites)
  • Anonymized message and activity data

Users could query Holos with things like "I'm planning a trip to Europe across these five countries — who should I meet up with?" or "I'm thinking about starting this business — who's already doing something similar?" Claude [tag="claude"] is already being used for assessment graph generation, and this would extend dramatically. James sees this as a potential revenue source — users would pay to access deep contextual intelligence over the network (47:06).

Sean noted this vision aligns beautifully with the platform's brand and aesthetic, and reframed his understanding of the project: it's not individual-to-individual networking, it's collectives, businesses, and collaborative initiatives finding each other through intelligent context (53:29).

[technology="Intelligent Matching Algorithms"]

🔧 Smaller Tactical Improvements

A working list of focused tasks James will convert into ClickUp:

  • User self-deletion of account and data (button needed; functionality exists)
  • Delete-a-Holon button and Leave-a-Holon functionality
  • Privacy settings for profile visibility (relevant since the map is now embedded on Hollow Movement's homepage)
  • Footer overlap fix on Holon pages where the wheel appears above it
  • Tooltips/labels on Holon edit page image indicators (users are confused about how to edit images)
  • Image attachments and emojis in messages — Sean to port from the surface implementation
  • Emoji reactions on messages (in addition to emoji posts)
  • Large Holon UI: cap visible member avatars with a "+X more" indicator and popup menu
  • Standardize member avatar styling to match the "viewing now" UI on the Wave page (small border matching background, slight overlap)
  • Make "About" the first tab on Holon pages
  • Force three admins minimum per Holon on signup
  • Future: Holon onboarding checklist similar to the profile creation checklist
  • Mobile responsive improvements on Hollow Movement site (oversized elements on wide screens, broken About page clamp system)

[technology="Custom Membership System"]

📋 Coordination & Working Rhythm

The team agreed on a lean coordination approach using ClickUp with priorities and views rather than heavy upfront scoping. Urgent + low-effort items (like the cookie bar) jump the queue. James and Sean will sync at least every other week to review progress and align on milestones (59:57).

James also emphasized following creative excitement: "It's important to follow your excitement" — Sean is encouraged to pursue the navigation design exploration since it aligns with his enterprise UX background (57:13).

The Hollow Movement budget situation remains favorable — the client pays invoices readily, and IRIS bills only team hours (not all of James's time), since much of what's being built will translate across other projects.

Action Items

James Redenbaugh

  • Convert all high-level domains and tactical items into ClickUp tasks with priorities and assignments (40:17)
  • Repropose the next phase scope and budget to the Hollow Movement team (10:39)
  • Lead LMS strategy: audit existing Supabase infrastructure, design course/lesson architecture, build out in Webflow components (12:36)
  • Build email notification system using n8n for unread messages and Holon updates (21:15)
  • Implement user account deletion, Holon deletion, Leave Holon, and privacy/visibility settings (24:31)
  • Force three-admin minimum on Holon signup (37:15)
  • Fix footer overlap bug on Holon pages where the wheel is visible (28:13)
  • Co-develop robust privacy policy with the Hollow Movement team (42:50)
  • Sign Sean's contract and send invoice (56:12)

Sean Graham

  • Priority: Port cookie consent bar from the floors project to Hollow Movement for GDPR compliance (26:46)
  • Implement image attachments and emoji posting in messages, plus emoji reactions, mirroring the surface implementation (29:51)
  • Build "+X more" member display pattern for large Holons and update avatar styling to match the Wave page's "viewing now" UI (32:53)
  • Add tooltips/labels on Holon image edit indicators to clarify editing controls (28:30)
  • Address mobile responsiveness on Hollow Movement site, especially the About page clamp issue (27:31)
  • Incrementally migrate custom code design system into Webflow components as features are updated (35:20)
  • Draft navigation redesign concepts in Figma exploring sidebar + consolidated menu patterns (56:29)
  • Set up Microsoft Clarity (or equivalent privacy-aware analytics) once cookie consent is live (40:40)
  • Review Michael Sean's feedback on the skills/tags UI on Hollow Movement and align with existing tag patterns (09:09)
Relevant Initiatives
No items found.
Transcript