Yo Operator!

Most enterprise systems — especially in construction — are complex, fragmented, and built around interfaces rather than outcomes. Users spend more time navigating systems than actually getting work done. The challenge was to explore: - what happens when interfaces disappear - how users interact with systems through intent instead of navigation - how AI can handle real operational tasks, not just assist The opportunity was to rethink software as something that acts — not something you operate.

I designed yoperator as a zero UI concept built around a conversational, skill-based AI operator. Instead of dashboards and menus, the system is driven by intent: users describe what they need — the system understands, orchestrates, and executes. The core idea: - a chat-first interface as the control layer - AI agents handling workflows behind the scenes - skill-based capabilities tied to real-world tasks I focused on: - designing how users express intent naturally - structuring agent capabilities into clear, actionable “skills” - prototyping flows where AI retrieves data, triggers actions, and guides decisions The system acts as an operator — not just a tool.

yoperator demonstrates how enterprise software can shift from interface-driven to outcome-driven. It shows: - how AI agents can take on real operational work - how complexity can be hidden behind simple interactions - how systems can become faster, more intuitive, and more aligned with real tasks The concept serves as a practical exploration of AI-native product design — where users don’t navigate software, they direct it.