The 30 ideas from nine people on your team’s October 7 wish list, plus Kelly’s October 15 idea from Slack. Most of them need one of three shared foundations, and building a foundation once makes every idea on it cheaper.
Brand conventions, Jamie’s voice, past reviewer feedback, processes and documents in one place that every team member’s AI reads from. This is Beth’s first priority.
| Idea | Who | What it needs from the brain |
|---|---|---|
| Concept-stage review tool | Kelly | Past feedback and brand guidelines |
| Style and consistency checker | Nikki | Not So Wimpy conventions, like “describing word” instead of “adjective” |
| Feedback database | Nikki | Every reviewer note, searchable while drafting |
| Feedback and review tracker | Kelly | The same feedback store, plus status |
| Product description and copy | Amanda | The standard description format and Jamie’s voice |
| Lesson Genie content engine | Erin | Jamie’s voice and new releases |
| Onboarding accelerator | Beth | Documents, project plans and who does what |
Kelly’s and Nikki’s ideas are one system seen from two sides. A single store of feedback and conventions can check a resource early, at the concept stage, and late, for style.
One database of every resource, with its description, grade band, standards, tags, activities and any facts that date. Katie and Erin asked for it outright, and more ideas read from it.
| Idea | Who |
|---|---|
| Product catalog, showing what exists and what’s overused | Katie |
| Lesson Genie product library | Erin |
| Search tags written from the final PDF | Amanda |
| Flag resources that will go out of date | Amanda |
| Grade-level differentiator and standards checker | Nikki |
| Product review, final file against what shipped | Katie |
| Clip art and font combinations for a new resource (added October 15) | Kelly |
| Bot library | Jamie and Beth |
The bot library depends on the catalog. A bot that writes review questions from a resource has to know the resource, so scoping the bots and starting the catalog are one piece of work.
One system that reads where teachers talk, in Facebook groups, DMs, support tickets, reviews, surveys and chat logs, and sorts it into their language, requests and complaints.
| Idea | Who |
|---|---|
| Voice of the Teacher | Beth |
| Social media activity tracker | Erin |
| Social media summaries and idea bank | Katie |
| DM support, pulling real questions out of ManyChat | Lindsay. The DM dashboard is already built, and finishing it covers this one. |
Beth’s, Erin’s and Katie’s ideas are one listening system with three different readers.
These build on the dashboards Scott already made.
| Idea | Who |
|---|---|
| Company pulse | Beth |
| Member risk tracker, which needs Lesson Genie data | Erin |
| Retention strategy simulator, once the risk tracker has data | Erin |
| Social media performance tool | Mary |
| Lead magnet performance | Beth |
| Idea | Who |
|---|---|
| Ad support, sending the freebie link to everyone who comments on an ad | Lindsay |
| Lead magnet manager, with tasks, landing page and Kit sequence held for Beth’s approval | Beth |
| Social media content planning, using Jamie’s skill pack | Mary |
| Graphics request hub, a form plus a workload estimate | Mary |
| Production status tracker | Kelly and Amanda |
| AI workload prioritization | Amanda |
On the production status tracker, Amanda wrote that the team has “gotten away from using the Monday production boards in the past year or so.” A tracker that updates itself from where the work already happens would help more than another board to keep current. It’s worth a short conversation about how production work moves today before anything gets built.