Strategy Meeting
Artifact info
Title:

Holomovement App — Wave Launch Strategy, Signup Flow Redesign & Broadcast Integration

Engagement:

Holomovement App Ecosystem

Client:

Holomovement

Meeting Date:
May 11, 2026
Next Meeting Date:
May 4, 2026
Hide This
April 27, 2026
Hide This
April 27, 2026
Hide This
April 27, 2026
Hide This
April 30, 2026
Hide This
April 20, 2026
Hide This
April 6, 2026
Hide This
March 25, 2026
Hide This
March 26, 2026
Hide This
March 30, 2026
Hide This
March 16, 2026
Hide This
March 9, 2026
Hide This
March 2, 2026
Hide This
February 25, 2026
Hide This
February 16, 2026
Hide This
February 19, 2026
Hide This
February 9, 2026
Hide This
February 2, 2026
Hide This
January 26, 2026
Hide This
January 22, 2026
Hide This
January 19, 2026
Hide This
January 14, 2026
Hide This
December 30, 2025
Hide This
People
Michael Shaun Conaway
James Redenbaugh
Hera Rose
Mariko Pitts
Artifact Image
Meeting Summary

🌊 Activation Day Strategy & Event Collaboration Vision

Michael Shaun Conaway opened with reflections from a strong funding call earlier in the day (00:11). The strategic upshot is to push Activation Day further into the world of collaboration — positioning it as the way "we collaborate together" across event organizers, communities, and individuals with projects to launch. Rather than treating the Wave as an annual moment, the team is exploring how to bring the Wave experience to other people's events throughout the year, contributing both philosophical content and a slice of the activation workshop format.

This opens conversations with potential partners like Vince, who floated the possibility of hosting something in Austin — whether a mid-year event or next year's Wave, contingent on sponsorship. Rachel noted that October is saturated with events, suggesting the better move may be to embed within existing events rather than compete. The shift is from transactional ticket exchanges toward intentional partnerships producing specific outcomes: catalyzing world-changing projects and collaboration at each touchpoint.

🏗️ App Infrastructure: Production vs. Development Environments

Michael Shaun raised the urgent need to separate the live app from active development, especially with the goal of putting 100 people on the app within the next week (03:53). James clarified the approach: rather than two fully distinct versions, the backend, data, and directory remain unified, but the custom scripts will be duplicated into production and development versions on Webflow [tag="webflow"]. A custom script will automatically serve the development version on a development domain, while the live domain at app.holomovement.net pulls the stable production scripts. Launching updates becomes a deliberate step of promoting development scripts to production.

James also confirmed fixes to location formatting — even verbose entries like "Austin, Texas, USA" are now automatically simplified to prevent layout breaks (05:50).

🔄 Signup & Profile Creation Flow Redesign

The current signup process takes 10–15 minutes with too many text areas and slides (06:39). James proposed a substantially streamlined approach designed in Figma 📄 and built with Webflow elements [tag="webflow"].

Public-Facing Landing & Preview Strategy

Before signup, visitors should be able to:

  • See the directory with profiles locked
  • See the map with profile previews (using a demo profile like "Jenny" or "Johnny Holomovement")
  • See a preview of the assessment without taking it
  • See the connection map as a blocked demo
  • Read the contribution / Engine for Good story on its own public page

[technology="Directory Systems"]

The New Bite-Sized Signup Flow

The redesigned flow asks only for essentials up front, then breaks deeper profile work into modular steps:

  1. Initial signup: name, email, password, location
  2. Quick profile creation: profile photo, domain, and tags
  3. Membership decision: contribute via Stripe [tag="stripe"] — yes or no
  4. Land in the directory and start exploring

From there, a checklist widget surfaces optional but encouraged modules:

  • Take the assessment — direct flow to the resonance assessment
  • Seeking & Offering flow — four sequential questions, with Claude [tag="claude"]-generated simplified statements and tags the user can edit before publishing
  • Complete your profile — short bio, purpose statement, AI-generated tagline suggestion, and an auto-generated banner the user can approve, regenerate, or replace
  • Skills self-assessment — name a skill and drag a bar, made into its own intentional flow

[technology="Custom Membership System"]

Checklist Widget Behavior

Michael Shaun strongly endorsed making profile completion a gate for connection features (13:12). The widget should appear as an icon with a notification dot, pop up as a modal when revisiting one's own incomplete profile, and absolutely surface when a user attempts to access connection features. This keeps onboarding bite-sized while ensuring users complete enough to make matching meaningful.

🤖 Connection Scoring & Matching

James confirmed the matching algorithm now weights three signals: shared domainsseeking and offering (weighted most heavily), and the resonance assessment (14:21). The system is working well; once the new flow ships, the checklist will explicitly guide users toward completing all three inputs to unlock meaningful connections.

[technology="Intelligent Matching Algorithms"]

📺 Wave Broadcast Integration Strategy

Two Distinct Audiences, Two Different Apps

Mariko drew a sharp practical line (32:11): the in-person attendees in Portugal are using Eventee 🔗 (eventee.com) for workshop signups, room logistics, and schedule changes — that's the on-the-ground event app and it's already designed. The Holomovement app is not trying to replicate that.

The Holomovement app's role is to be the home for the global broadcast audience and the meeting place where in-person and online communities mingle. Online ticket buyers (currently routed through Ticket Tailor 🔗) need an access communication that directs them into the app as their primary destination — "it would be a massive failure if we don't send people to the app."

Broadcast Page Architecture

James proposed embedding whatever Peter and the broadcast team deliver (likely a Hubcast or YouTube embed) onto a member-protected custom Wave page inside the app (37:22). Three features layer on top:

  • Live profile sync — see who else is currently watching
  • Member wall — copy the Holon wall pattern for chat and posts during the broadcast
  • Breakout room — an always-open audio-only room using the breakout system James has working (medium complexity to integrate with profiles)

[technology="Video Conferencing Solutions"]

Engine for Good as Donation Framing

Mariko suggested that since broadcast tickets are effectively donations, the membership flow could acknowledge: "If you purchased a Wave ticket, this one-time donation goes directly to the Engine for Good" (42:11). This keeps the contribution narrative clean and doesn't require special auth gating for paid vs. unpaid broadcast viewers — the page is simply member-protected.

Wave Attendee Tagging — Keep It Simple

Hera floated several ideas including notifications, holon-style groups, and an AI agent monitoring a living news feed (29:51). Michael Shaun firmly steered toward the most conservative path possible given the three-week timeline (30:54): just use a tag. Anyone can self-select a Wave 2026 tag (and potentially Wave Broadcast 2026 as a distinct colored tag), and the directory can filter by it. No new code, no new taxonomy, no risk of breaking core flows during the event. The team aligned on protecting development time for stability of what's already built.

[technology="Community Facilitation Tools"]

🧪 Breakout Room Testing & Safety

The breakout room concept is exciting but carries real risk. Michael Shaun insisted on prefacing it as beta and, critically, requiring the core team to hold a meeting on it next week before any public exposure (47:05): "If we can't hold a core team meeting on the damn thing, we shouldn't be turning it loose on the public." James will:

  • Connect the breakout room to user profiles
  • Disable video initially (audio-only reduces bandwidth and privacy friction)
  • Send test links for a group test

Mariko raised community moderation — a red-flag system where after three flags a participant goes dark or is removed. Worth exploring but not blocking for Wave.

🎨 UI Refinements & Holon Visualization

Michael Shaun flagged that on a full Holon, the gradient overlay obscures member faces (50:32). James explained the gradient was designed for when membership exceeds the visible count — at that point profiles rotate through and fade. Current numbers sit awkwardly in a static state. Fix: reduce gradient intensity and ensure rotation behavior triggers appropriately on larger Holons.

The team also reviewed quality-of-life updates including category cards with bleeding color, a new red-orange ("signal red" / blood orange) tone for notifications that reads as curious rather than alarming, and a flatter version of the proposed app icon for the nav.

💭 App Naming — Holosphere & Beyond

The naming conversation continues. James proposed Holosphere, with a 3D logo concept. Michael Shaun's feedback: the logo could work but should be flatter and less reflective — currently reads a bit like glossy spaghetti tubes. Other candidates floated: HolospaceHollow FieldHolocene. The group is converging on the practice of waiting to see the thing before naming it — "like getting a dog, you should hang out with her for a couple weeks." Launching at the Wave without a final name is acceptable; arriving with one would be a bonus.

🎤 James Speaking at the Wave

A meaningful decision: James will take the stage Saturday morning to introduce the app, its vision, and the invitation to participate (58:28). Mariko made the case strongly — as the developer holding the build, James can speak with technical authority about what's been co-created, why it matters for the broader ecosystem of communities asking for this kind of tooling, and what's next. This positions him as the face users can approach, and frames the app as the most important "what's next" for the Holomovement.

The slot lands right before the coffee break, allowing attendees to immediately scan a QR code and create profiles. The talk will mirror the landing page narrative — laying out what's built, the roadmap, and the why — making a strong invitation not just to sign up but to remain part of the app's evolution.

[technology="Collaboration Management Tools"]

Action Items

James Redenbaugh

  • Set up production vs. development script duplication on Webflow [tag="webflow"] with automatic domain-based serving, and add the promote-to-production step to the launch process (04:19)
  • Deploy the redesigned signup flow (essentials only) and modular profile creation checklist; ready for testing by end of week (06:39, 17:35)
  • Implement the Seeking/Offering, Complete Your Profile, and Skills Self-Assessment flows as discrete modules with Claude-generated [tag="claude"] suggestions users can edit (10:00)
  • Build the Wave broadcast page with embedded stream, member protection, live profile sync, member wall, and audio-only breakout room (37:22)
  • Connect breakout room to profiles, disable video, and send test links for core team group test next week (47:43)
  • Reduce Holon gradient intensity and verify rotation triggers on full Holons (50:32)
  • Add admin-only visibility toggle for the in-app roadmap/app map (20:06)
  • Draft landing page story articulating purpose, roadmap, and why — share iteratively for rapid feedback (01:06:10)
  • Prepare Saturday Wave talk with accompanying visuals previewing the app and inviting participation (01:02:47)

Michael Shaun Conaway

  • Send James and the team the Engine for Good 📄 write-up to integrate into landing page and membership messaging (01:07:19)
  • Coordinate with Mariko on Saturday morning stage scheduling, including James's app talk and the micro-grant award placement (01:00:01)
  • Continue monitoring app naming conversation toward post-launch resolution (55:19)

Mariko Pitts

  • Write up the global broadcast attendee experience spec and coordinate with Peter on broadcast embed technical details (40:36)
  • Confirm Wave Broadcast 2026 colored tag and ensure ticket buyer email communications direct viewers into the app (40:36)
  • Schedule James's speaking slot and onboarding for the Saturday morning plenary (01:05:27)
  • Order printed rollups and finalize launch marketing collateral once naming direction is set (56:16)
  • Participate in breakout room and group chat testing with the core team next week (47:00)

Hera Rose

  • Continue refining ideas on Wave attendee experience, notifications, and community grouping for post-Wave iterations (24:46)
Relevant Initiatives
No items found.
Transcript