Automation only works when it’s paired with someone who actually knows the problem being automated. An automation expert can build a system that senses, moves, and controls with precision — but without someone who deeply understands the actual work being replaced or assisted, that capability has nowhere useful to land. This pairing is the collaboration pattern behind every project on this site, and I think it’s also the pattern behind applying automation successfully almost anywhere.
The subject-matter expert’s contribution isn’t just information — it’s judgment that took years to develop and is easy to underestimate from outside the field. A pizza maker knows when dough feels right, not just what a recipe says. A curriculum designer knows what actually holds a middle schooler’s attention, which is a completely different skill from knowing what a university robotics student needs. An automation expert who skips this step and tries to automate a process they don’t actually understand tends to build something technically impressive and practically wrong.
This project treats that pairing as a genuine two-way collaboration, not automation experts extracting knowledge from an SME and then working alone. EduBot is a clear example of how many distinct kinds of subject-matter expertise a single project can actually need: robotics and manufacturing knowledge to get the hardware right, curriculum and pedagogy expertise (which itself splits by audience — engaging a middle schooler is a different skill from designing a university-level or ROS-based curriculum), people who’d actually deliver instruction, and people who understand how to reach the right audiences at all. Pizza is a simpler illustration of the same idea in a completely different domain: someone who actually knows how to make good pizza, paired with someone who can automate the process — potentially through an arrangement as direct as the pizza-cart collaboration idea described elsewhere on this site, where a partner keeps the pizza profit while helping build the automation alongside it.
The reason this pattern matters beyond any one project: it’s what makes the whole “automation experts pairing with SMEs” method repeatable across markets that otherwise have nothing in common. An automation expert doesn’t need deep prior knowledge of greenhouses, or dairy farming, or classroom teaching. They need the discipline to find and genuinely listen to the person who does. (See Repeating Automation Patterns for the technical side of what gets applied once that pairing is in place, and Build Something Similar for how this method could extend beyond this project’s own markets.)