Just a few years ago, instructing software meant learning its rigid language or clicking through predefined interfaces. Today, the landscape has flipped: we regularly see a marketing manager typing phrases like 'proceed with the plan, but make it more direct and with a light tone' to an AI like Claude or Gemini. Or even invoking sci-fi movie lines like 'make it so' or 'hit it' to kickstart a task.
This temporal contrast isn't just an anecdote. It reveals a profound trend: interaction with AI is becoming increasingly conversational and intuitive. A recent Reddit discussion, titled 'What's everyone's clever "proceed with plan" commands?', highlighted this very phenomenon. Users and developers share their favorite phrases to tell AI to move forward with a task after it has presented an action plan. Beyond the fun of movie quotes, a clear need emerges to control the execution of AI agents with precise, personalized signals.
The Art of Command: What it Means for Italian SMEs
The Reddit thread, which you can find here: Reddit /r/ClaudeAI, isn't just about slang preferences. It underscores three key points with a direct impact on Italian SMEs approaching AI:
- More than a 'magic word,' it's a structured signal of intent: Commands like 'proceed' or 'execute' are not just synonyms; they often convey nuances the user wants to impart to the AI. A 'make it so' might imply trust and delegation, while a more formal 'proceed with the following modifications' suggests an active review. For a company implementing an AI agent for lead generation or data analysis, the clarity of these signals is crucial for output quality.
- Reflects a desire for human control and iteration: Users don't just want to delegate; they want to guide. Seeing the AI's plan and giving the go-ahead with a specific command is a way to maintain control over the process, correct the course before execution, and ensure the AI operates in line with business objectives. For example, in a B2B service company with twenty employees, an AI agent supporting proposal drafting might generate a draft, and the team wants final say on the direction before the agent proceeds with final processing or further content generation.
- Interaction personalization becomes part of company culture: While a 'hit it' might seem informal, adopting a common language for interacting with AI can strengthen team cohesion and speed up processes. This interaction style, which deviates from the rigid interfaces of traditional software, requires a deeper understanding of natural language and user psychology. This dynamic is crucial for safeguarding company knowledge, as we explored in a previous article.
Practical Impact: What Changes for Developers and Decision-Makers in Italy
For a CTO or SME founder, these observations translate into concrete actions:
- Advanced and iterative Prompt Engineering: It's no longer enough to provide a good initial prompt. It's essential to design agent architectures that include feedback loops and continuation commands. This means the AI must be able to present an 'intermediate status' or an 'action plan,' await human input (the famous 'proceed'), and then continue. Orchestration tools like n8n or custom agents based on Gemini, Claude, or GPT SDKs should be configured to support these multimodal and iterative interactions.
- User Experience (UX) for AI: User interfaces must evolve. We're not just talking about chat boxes, but environments that allow viewing the AI's 'thought process,' intervening with specific commands, and evaluating progress. A software development company with a team of 15-20 people integrating AI for code analysis might want an interface where the AI proposes corrections, the team reviews them, and then with an 'accept and implement,' the AI proceeds, perhaps by generating commits or unit tests.
- Training and Cultural Adaptation: Adopting AI agents that require more conversational management implies a learning curve for teams. Encouraging the use of clear and internally standardized commands can optimize efficiency. At Logika.studio, we observe that defining interaction protocols, even informal ones, with AI agents reduces ambiguity and accelerates the development of solutions like those we present in our documented projects.
Known Limitations and When NOT to Use Overly Conversational Approaches
Despite the benefits, there are limitations to consider:
- Costs and Latency: Overly long or elaborate commands increase context size and, consequently, inference costs and response latency. For high-frequency or time-sensitive tasks, brevity and clarity are still priorities. The goal is efficiency, not mere creative expression.
- Variations Between Models: Not all AI models respond to informal commands in the same way. The consistency of agent behavior can vary significantly between a local open-source model and a more advanced cloud API. It is crucial to test and standardize the approach with the specific model in use.
- Risk of Ambiguity: While informality can be fun, excessive freedom in commands can lead to ambiguity and unexpected results. For critical processes or those with a strong business impact, formality and precision in language are indispensable.
In summary, 'proceed with the plan'—whether it's an informal 'make it so' or a rigorous 'execute instructions'—is not just a community curiosity. It's a symptom of how human-machine interactions are evolving, offering Italian SMEs more powerful tools to control and personalize their AI agents. Understanding this dynamic means knowing how to design more efficient and user-friendly systems, transforming mere automation into true collaboration.
Logika.studio applies these patterns in the projects we document — concrete interventions in software, AI, marketing, and trading.
