Why I Oppose Overly Complex Systems: Lessons from 2000s Failures

My business journey, which began in the 90s, taught me one important truth: complexity is the enemy of efficiency. This became particularly evident in the 2000s when, as a director, I tried to implement various automation and CRM systems, facing a series of failures. This very experience became the foundation of the philosophy I embed in formspace.design — a landscape planning tool where simplicity and practicality come first.

The Beginning of the Journey: From Euphoria to Disappointment in the 90s and 2000s

In the early 90s, working as a deputy director at NPF Alkar, I was already assigning tasks to programmers for management accounting. Back then, it seemed like the pinnacle of technology – the ability to systematize data and control processes. With the advent of the 2000s and the development of the internet, so-called 'off-the-shelf' CRM and ERP systems appeared on the market. They promised a revolution in management, complete automation, and transparency of all business processes. Like many executives, I succumbed to this euphoria. It seemed like the solution to all problems: one system that would bring together sales, finance, projects, and customer relationships. We spent significant funds on purchasing licenses, implementation, and training. However, reality quickly dispelled these rosy expectations.

Why Complex Systems Failed to Take Root: Key Mistakes

My experience showed that most implementation attempts ended either in partial use or complete rejection. Here's why:

Feature Bloat

Developers aimed to cram as many features as possible into systems to cover a wider range of potential clients. As a result, 80% of functions remained unused. For example, for the company 'Dom i Sad' (House and Garden), where we designed and built cottages and did landscaping, we were offered modules for freight logistics management or complex warehouse analytics, which were completely superfluous. This overloaded the interface, distracted, and irritated employees.

High Barrier to Entry

Training staff to work with such systems turned into a multi-month marathon. People accustomed to their notebooks and simple spreadsheets struggled to master complex interfaces and convoluted algorithms. Resistance to change was colossal. I myself encountered situations where employees preferred to keep records the old-fashioned way, just to avoid dealing with the new, 'smart' system. I wrote about this in detail in the article Why contractors manage clients in notebooks, not systems: I did it myself.

Expensive Support and Customization

Constant modifications for specific business needs cost a pretty penny. Any minor change, be it a new report or a workflow adjustment, cost between $1000 and $2000 and required weeks of waiting. This created dependence on contractors and made the system inflexible.

Detachment from Real Needs

Developers often created systems 'in a vacuum,' without a deep understanding of the specifics of real business. What looked logical on paper turned out to be impractical in the field. For example, landscape design requires tools for visualization, working with scales, and quick volume estimation, not universal financial calculators.

The Importance of the 'Human Factor' and Interface Simplicity

People are not robots. They use tools that are convenient for them. If a system requires too much effort to learn or perform basic tasks, it will be rejected. This rule is universal for any age and any field. My experience at 61, when I started coding independently with the help of AI, confirmed this: even with powerful technologies, if a tool is inconvenient, it won't catch on. A typical mistake of managers is to demand that users change their habits instead of adapting the system to the natural workflow.

Lessons from the Landscape Business: What's Really Needed on a Plot

Working at 'Dom i Sad' (House and Garden) since 2000, where we designed and built cottages and landscaped plots ranging from 6 to 20+ ares, gave me a deep understanding of the needs of landscape designers and plot owners. Here, universal ERP systems are not what's needed, but very specific solutions:

• Quick Visualization: The ability to show the client what their plot will look like.
• Simple Zoning: A convenient tool for dividing a plot into functional zones.
• Plant and Object Libraries: Easy access to information and the ability to add them to the plan.
• Quick Change Capability: Clients often change their preferences, and the system must support this without redrawing the entire project.

These are the pain points I aimed to solve when creating formspace.design.

Principles I Embed in formspace.design

All my past experience, both as a business consultant in the 90s and as a director of a landscape company, shaped the logic and principles of formspace.design:

• Practicality: Every module and every function must provide real benefit and solve a specific problem, without redundancy.
• Intuitiveness: The system should be understandable at a 'pick up and use' level, without multi-hour courses. I design the interface so that even a novice can start working within 15-20 minutes.
• Flexibility: The ability to quickly make changes and adapt the project to changing conditions.
• Accessibility: formspace.design is created not only for 'IT specialists' but also for landscape design practitioners. My own journey in development, where I started coding with AI at 61 without a specialized education, proves that with subject matter expertise and discipline, it is possible.
• Focus on the Essentials: Separating routine tasks that AI can perform from creative solutions that require human experience. I wrote more about this in the article What AI can calculate, and what only you know from experience.

How to Plan in formspace.design Using the Principle of Simplicity

Imagine a client approaches you with a request to re-plan a 10-are plot. They want to divide it into recreation areas, a garden, and a vegetable patch, but have no clear idea of how it should look. Here's how you can use formspace.design, following the principle of simplicity:

Start with Module 1.x 'Plan/Zones/Objects'. Upload the plot plan (or draw it from scratch). Then, using intuitive tools, quickly outline the main functional zones: terrace, lawn, playground, vegetable patch. You don't need to think through every detail immediately; general outlines are sufficient. The module allows you to drag and drop ready-made objects (gazebos, benches) and see how they fit into the overall picture. This step takes about 30-40 minutes, not days, as with complex CAD systems.

Next, move to Module 2.1 'AI Concept'. Describe your wishes and the client's preferences in a few sentences, for example: 'Modern style, lots of greenery, barbecue area, small pond.' The AI will generate several concept variations, using the landscape design principles embedded within it. You will receive not just abstract pictures, but concrete ideas for zoning and content that can be discussed with the client. This allows you to quickly get working concepts without spending weeks on detailed elaboration of each option. And finally, Module 3.1 'Design by Photo' will allow you to overlay the chosen concept onto a real photo of the plot, so the client can see how their idea will come to life, without the need to create complex 3D models.

FAQ

Why do large corporations use complex systems, but small businesses don't?

Large corporations often have a staff of IT specialists, unlimited budgets for implementation and support, and a complex hierarchy requiring multi-level control. For them, feature bloat might be justified, as they might use only a small part, but that part will be critically important for a specific department. Small businesses cannot afford this; they need maximum return from each function and minimal maintenance costs.

How to distinguish a useful feature from a redundant one?

A useful feature is one that solves a specific, recurring problem in your daily work and saves you time or resources. A redundant feature is one you use once a year (or not at all), or one that duplicates the capabilities of other, simpler tools. Always ask yourself: 'How often will I use this, and what specific problem will it solve?'

Can AI simplify an overly complex system?

AI can help automate routine tasks and analyze data, but it cannot make an inherently complex interface intuitive or remove redundant features. AI is a tool that enhances the logic embedded in a system. If the logic is convoluted, AI will only guide you through that labyrinth faster, but it won't make it simple.

How expensive is the support for simple systems?

Support for simple systems is significantly cheaper because they require fewer resources for maintenance, updates, and staff training. The fewer complex integrations and customizations, the lower the cost. My experience shows that simple systems cost 5-10 times less in annual maintenance than their overloaded counterparts.

What is the optimal implementation period for a new system?

The optimal implementation period for a simple system for a small business is from a few days to 2-3 weeks for full mastery of basic functions. If it takes months, that's already a red flag, indicating excessive complexity or a poorly thought-out training methodology. For formspace.design, I aim for users to be able to start working within a few hours.

What if my team resists new tools?

Resistance to new tools is often caused by fear of the unknown, fear of losing familiar control, or an inability to master something complex. It's important to show the team how the new tool will simplify their work, not complicate it. Start with training using real examples, emphasize that the system is intuitive and requires minimal learning. Involve employees in the selection and testing process so they feel a sense of ownership.

Isn't formspace.design too simple for professionals?

Not at all. The simplicity of formspace.design does not mean primitiveness. It means we've removed everything superfluous, leaving only the functions truly necessary for quality landscape planning. Professionals value tools that allow them to solve tasks quickly and efficiently, rather than spending time battling with an interface. Our system allows you to focus on creativity and expert solutions, while routine tasks are delegated to AI.

How to tell if a system is outdated and a new one is needed?

A system is outdated if it slows down your work instead of speeding it up; if simple tasks require many unnecessary steps; if it doesn't integrate with modern tools or support current data formats. Another sign is constant errors, crashes, and the need for workarounds. If your current system causes more headaches than benefits, it's time to look for a simpler and more effective solution.

My path to formspace.design is a conscious choice in favor of simplicity, efficiency, and practicality, based on years of experience with both successful and failed implementations. I am convinced that a truly valuable tool is one that helps you achieve your goals, rather than creating new problems with its complexity. I invite you to try formspace.design and see for yourself. Start planning your plot today, without unnecessary complexities or barriers.