Joint
Signed out · public view
Owner sign inLoading snapshot…
Loading snapshot…
Doyung · Ad hoc
Read-only. Sign in as owner or team to move cards.
Joint
AfricAI
AfricAI
AfricAI
AfricAI
AfricAI
Akil Wade
AfricAI
Joint
Akil Wade
AfricAI
Akil Wade
AfricAI
Akil Wade
Akil Wade
Akil Wade
AfricAI
AfricAI
AfricAI
Akil Wade
AfricAI
AfricAI
AfricAI
AfricAI
Akil Wade
AfricAI
Akil Wade
AfricAI
Akil Wade
AfricAI
AfricAI
Joint
Akil Wade
Akil Wade
AfricAI
AfricAI
Akil Wade
| # | Title | Angle | Goal | Status |
|---|---|---|---|---|
| 1 | Why I am building mAIstro | Why I curate AI experiences | Attendee trust | Recorded |
| 2 | Turn one tutorial into an event workflow | Turn one tutorial into a test | Reach | Recorded |
| 3 | Make it easier for the right people to meet | Explain luck engineering | Secondary draft | Secondary draft |
| 4 | Your event calendar needs room for your life | Be the maestro of your life | Reach | Recorded |
| 5 | Choose speakers for the work they can explain | Show the curation filter | Production expertise | Recorded |
| 6 | What AfricAI and mAIstro each do | Say what AfricAI does | Production expertise | Recorded |
| 7 | Put specific African work in the room | Africa helps shape the next chapter | Attendee trust | Not recorded |
| 8 | Map your event before choosing AI tools | Three lessons from Nate Herk | Reach | Not recorded |
| 9 | The handoff is part of the system | Three lessons from Liam Ottley | Reach | Not recorded |
| 10 | Give an AI workshop one useful job | Three lessons from Brilla AI | Reach | Not recorded |
| 11 | Help the person who arrives alone | Come with one good question | Attendee trust | Not recorded |
| 12 | Give networking a starting point | The conversation between talks | Attendee trust | Not recorded |
| 13 | Speakers need a promotion handoff | Show the content handoff | Reach | Not recorded |
| 14 | Review more than the highlight reel | Choose what to carry forward | Production expertise | Not recorded |
| 15 | An invitation to the next AfricAI | Invite people into the next chapter | Attendee trust | Not recorded |
| 16 | What I help event companies do | Make your introduction useful | Reach | Not recorded |
| 17 | Keep approval visible | Ask where judgment stays | Attendee trust | Not recorded |
| 18 | Connect what you already use | Look for the trade off | Reach | Not recorded |
| 19 | Start with the reason for the room | Start the event brief here | Production expertise | Not recorded |
| 20 | Give the community a reason to continue | Give your follow up a reason | Reach | Not recorded |
| 21 | Keep inspiration with its source | Write notes an editor can use | Reach | Not recorded |
| 22 | Test the registration journey yourself | Watch the second demo | Reach | Not recorded |
| 23 | One useful workflow can stand on its own | Give your first experiment edges | Reach | Not recorded |
| 24 | The running order needs a handoff | The transition has a job | Production expertise | Not recorded |
| 25 | Choose the perspectives your audience needs | Ask whose knowledge is missing | Production expertise | Not recorded |
| 26 | Test one complete event workflow | Test one complete piece | Reach | Not recorded |
| 27 | Collect feedback you can act on | Make feedback usable | Attendee trust | Not recorded |
| 28 | Installation and production are different jobs | Bring us the audience problem | Enquiries | Not recorded |
| 29 | Keep sponsor promises in the plan | Keep the source attached | Creator credit | Not recorded |
| 30 | Why I am starting with AfricAI | Turn Africa is next into action | Identity | Not recorded |
| 31 | Build the first useful version | Thinking | Reach | Not recorded |
| 32 | Plan check in before the room fills | Plan the first minute | Production expertise | Not recorded |
| 33 | Selling a ticket and receiving cash are different | Ask for the task | Reach | Not recorded |
| 34 | Give attendees time to try something | Leave room to use it | Production expertise | Not recorded |
| 35 | An introduction needs agreement | Connect people with a reason | Reach | Not recorded |
| 36 | Rehearse the recovery | Rehearse the backup | Production expertise | Not recorded |
| 37 | How I am packaging the help | Private AI workshops for your team | Private team workshop enquiries | Not recorded |
| Day | Piece | Format | Ask |
|---|---|---|---|
| 01 | Why I curate AI experiences | Reel, joint with Akil, city/date end card | Ask what would make the experience useful |
| 02 | Turn one tutorial into a test | Carousel | Choose one task for a saved tutorial |
| 08 | Three lessons from Nate Herk | Reel, source credit | Save and sketch one repeat task |
| 06 | What AfricAI does | Reel | Follow the thinking behind the next experience |
| 03 | Prepare before opportunity appears | Carousel | Name one thing to prepare |
| 11 | Coming on your own | Reel | Share the question you would bring |
| 07 | Africa helps shape the next chapter | Reel, joint, end card | Recommend an African builder |
| 09 | Three lessons from Liam Ottley | Reel | Try one everyday task this week |
| 16 | Introduce your project clearly | Carousel | Say yours in one sentence |
| 12 | The conversation between talks | Reel | Save the three questions |
| 05 | How the curator thinks | Reel | Identify learning value of one shortlisted person |
| 22 | Look carefully at a demo | Carousel | Save for next AI demo |
| 14 | What to carry forward | Reel | Name a question footage cannot answer |
| 15 | Cape Town invitation | Reel, joint, date on screen | Save the date and follow |
| 10 | Three lessons from Brilla AI | Reel, credit George Boateng and team | Identify local context to test |
| 23 | A useful starting point | Carousel | Try comparison with sample text |
| 19 | Start the event with a brief | Reel | Put three answers atop your brief |
| 04 | Choose where your judgment belongs | Carousel | Write the outcome before the next prompt |
| 24 | Why transitions matter | Reel | Write one sentence between sessions |
| 25 | Different kinds of expertise | Reel | Check brief for missing perspective |
| 21 | Notes an editor can use | Carousel, end card | Save the four headings |
| 28 | What to put in an event brief | Reel | Message AfricAI |
| 20 | Make a follow-up specific | Carousel | Check detail and question |
| 29 | Why creator credit matters | Reel | Tag AfricAI in original post |
| 17 | Ask a builder a better question | Reel | Save that question |
| 18 | Learn the trade-off | Carousel | Save three headings |
| 27 | Give useful event feedback | Reel | Try that structure |
| 13 | The content handoff | Carousel | Check one clip handoff |
| 26 | Test before committing | Carousel | Choose the smallest piece |
| 30 | Turn Africa is next into action | Reel, end card | Choose one piece of work to learn from |