Open InfoTech Solutions

Open InfoTech Solutions

Software Development and Cloud Consulting

T830.360.1920
Email: info@oitsol.com

Open InfoTech Solutions
New Braunfels, TX

Open in Google Maps
QUESTIONS? CALL: 830.360.1920
  • Solutions
    • Software Development
      • Integrations
      • WordPress Plugins
      • Legacy Systems
      • Save My AI Project
      • Own Your Automation
    • Cloud Services
    • Fractional CTO/CIO
      • Your Guide to Fractional CTO Services
  • Tech Blog
  • Case Studies
    • Camera Snapshot System
    • Payroll Processing System to CRM
    • Project Accounting
    • Unlimited Car Wash WordPress Plugin
    • Walks for Recovery
    • Web Donation to Raiser’s Edge Plugin
    • Rent Payment Plugin for WordPress
  • About Us
FREEEVALUATION

Author: oit-wpadmin

Why Custom MCP Servers Are Becoming a Core Part of Modern AI Architecture

Saturday, 17 January 2026 by oit-wpadmin

As AI systems move from experimentation into real production workflows, organizations need a secure, governed way to connect models to company systems and data. That’s where MCP servers are quickly becoming essential.

Custom MCP Servers

Summary

  • 1MCP servers provide connectivity and control for how AI systems use and interact with your company data.
  • 2A custom-built MCP server improves security, governance, and reliability by enforcing your policies at the point of AI access.
  • 3Low-code / no-code MCPs are best for prototyping—they can fall short for scalability, security, and mission-critical workloads.
  • 4Serious AI adoption requires treating MCP infrastructure as software, not just something to configure.


What MCP Servers Do (and Why They Matter)

MCP servers provide tools that allow modern AI systems to connect to resources beyond what they’ve been provided in a single model context.
That might be your accounting system, your CRM, or a custom internal platform.

Why “just use existing APIs” often breaks down

  1. APIs often return too much. They’re designed for applications, not for context-limited AI tool use, so they may return bulk data
    instead of only what the AI needs for the current task.
  2. APIs don’t always provide the right control model. Some are all-or-nothing, others are constrained by the connected user,
    and many lack granular guardrails.
  3. APIs can limit visibility. It’s often hard to see exactly what was requested, what was returned, and what the AI did next.

With an MCP server, you can provide exactly what’s needed for the specific interaction—no extra content to confuse the AI,
and no unnecessary functionality that expands your risk surface. You can also track, audit, and adjust tool behavior based on
predefined rules the AI can’t override.

MCP and Security Posture

You’ve likely seen the headlines: “We told AI not to delete the database… but it did it anyway.”
MCP can be the secure entrance into your data and network—but not all MCP servers are created equal.

Common pitfalls with hosted or generic MCP servers

  • Over-broad permissions
  • Hardcoded credentials
  • Lack of auditability
  • Limited isolation between tools or data sources

Custom MCP servers let you apply your security principles to AI interactions—identity, access boundaries,
auditing, and policy enforcement—without relying on generic assumptions.

Low-Code / No-Code MCPs: When They’re Useful and Where They Fall Short

When to use low-code / no-code MCPs

  • Experimentation and internal testing
  • Prototyping workflows
  • Validating a use case before engineering investment

Where they fall short

  • Coarse-grained permissions
  • Limited support for custom authentication flows
  • Limited visibility into parts of the process
  • Weak audit and compliance capability
  • Hard to version, test, and govern

Low-code MCPs optimize for speed and reduced engineering effort—not for control.
That tradeoff is fine during exploration, but it becomes a liability in production.

Production MCP Servers Require Real Code

Why code matters in production

  • Security policies are logic, not just GUI configuration
  • Real error handling and retries that surface actionable failures
  • Domain-specific validation and guardrails (what “safe” means depends on your business)
  • Testability (unit, integration, security testing)
  • CI/CD, version control, and rollback support like the rest of your platform

Don’t cut corners: if MCP is part of your production AI stack, it should meet the same standards as the rest of your software platform.

Choosing the Right MCP Strategy for Your Organization

Use these questions to pressure-test whether you need a custom MCP server:

If the answer to any of the above is yes, building a custom MCP server is typically the better long-term choice.

Looking Ahead: MCP as a Long-Term Control Plane for AI

MCP servers are evolving into a three-part bastion for modern AI:

1) Policy enforcement

Control what AI can access and what actions it can perform—at the boundary where it matters.

2) Governance and visibility

Centralize audit trails, usage patterns, and operational accountability across AI tools.

3) Shared enterprise structure

Create a consistent integration pattern for teams building AI capabilities across the organization.

Organizations that invest early in custom MCP servers can achieve a stronger security posture, faster iteration with AI,
and lower long-term risk.

Building AI responsibly requires more than prompts and plugins.

If you’re moving beyond experimentation and into real-world AI systems, your MCP strategy matters.
Let’s talk about designing an MCP architecture that scales securely—from prototype to production.

Schedule a meeting with a developer

Read more
  • Published in Technology
No Comments

When Zapier Stops Scaling: 7 Signs It’s Time to “Own Your Automation” (and a Safe Migration Playbook)

Sunday, 11 January 2026 by oit-wpadmin

When Zapier Stops Scaling: 7 Signs It’s Time to “Own Your Automation” (and a Safe Migration Playbook)

Imagine this. A request comes through to tweak a field in your CRM to a different data type. A member of the IT team makes the change and confirms it is working as intended. Within two hours, there are 12 alerts in Zapier that no-code workflows are failing. The blame game begins. While some of the zaps take a few minutes to fix, there is one that has to be completely re-designed, and one that should be working, but just isn’t.

While this exact scenario is fictitious, I’ve seen similar situations play out—situations where there are flows that people would like to change but don’t touch because each time someone does, it breaks for hours or days.

This may sound like I’m disparaging no-code and low-code workflows, but they have a very good place: initial automation, prototyping, non-critical workflows, and multi-step processes.


Seven Signs It’s Time to Convert a Workflow to Owned Code

  • Volume is high, and costs and completions have become unpredictable.
  • The workflow is mission-critical (you lose significant revenue when it isn’t functioning).
  • Tool sprawl (e.g., Zapier + Make + Sheets + internal scripts).
  • Debugging and updates are difficult—or rely on a single person.
  • You need clarity behind the workflows (logs, metrics, better alerts).
  • Security and compliance concerns have become major issues (where is this data at all times? what is the cleanup time on temporary data?).
  • You care about intellectual property and business value (valuation and M&A readiness). Asset vs. liability.

Start With Confirmation of How Much You’re Spending on Workflows

What to measure:

  • Number of automations
  • Average number of failures per month
  • Average time to repair
  • Time spent fixing workflows each month

Although estimating the cost of converting workflows is difficult without specific details, expect an initial upfront expense followed by ongoing hosting fees. If you’re already spending over $100 per month on workflows, plan to save at least 80% annually after the conversion.

The key questions are the cost of developing the new code, how valuable the new code is as an asset versus a dependency, and whether there is capital available for the initial investment.


Migration Playbook

1) Inventory Your Automations

  • List workflows, triggers, connected systems, data moved, and owners.

2) Define the System of Record for Each Domain

  • Identify the single source of truth for each domain (customers, billing, payroll, projects, etc.).
  • Note: multi-master bi-directional workflows are possible but problematic.

3) Convert the Highest-Impact Workflow First

  • Pick one that is high-volume, high-friction, and high-risk.

4) Build It as a Small Service With Guardrails

  • Validation rules
  • Idempotency (duplication, replays)
  • Retries
  • Rate-limit handling

5) Run in Parallel for a Safe Cutover

  • Compare outputs
  • Check edge cases
  • Switch half of traffic—or all of traffic—when confident

6) Add Observability and Ownership

  • Logs, metrics, alerts, and documentation for handoff

The Results

  • Predictable cost
  • Fewer failures + faster debugging
  • Better security posture
  • Easier onboarding for new team members
  • Automation becomes an asset—not a subscription

Practical Examples

  • Payroll system to CRM
  • Donations to the fundraising system-of-record

Need help? Contact us for an automation audit.

Share 2–3 workflow examples with us, and we can help you understand the potential ROI from conversion.

Schedule with an engineer today

Read more
  • Published in Technology
No Comments

What Is a Fractional CIO or CTO — and Why Your Business Might Need One

Thursday, 01 January 2026 by oit-wpadmin
The Role of A Fractional CIO/CTO

What Is a Fractional CIO or CTO — and Why Your Business Might Need One

As organizations grow, technology decisions become more complex, higher-risk, and more tightly connected to business outcomes.
A fractional technology leader can bring executive-level guidance without the overhead of a full-time hire.


Many companies reach a stage where they need senior technology leadership—without needing or justifying a full-time executive role.
That’s where a fractional CIO (Chief Information Officer) or fractional CTO (Chief Technology Officer) comes in.

What “Fractional” Means

A fractional CIO or CTO provides experienced, executive-level technology leadership on a flexible, part-time basis.
This model gives organizations access to strategic oversight, planning, and decision support—scaled to their actual needs.

At Open InfoTech Solutions, fractional leadership is intentionally flexible. Whether you need a few hours per week,
periodic support for planning and budgeting, or deeper involvement during a major initiative, the engagement adapts to your business.

Why Not Rely Solely on Your Managed Service Provider (MSP)?

MSPs are great at:

  • Keeping systems running
  • Responding to issues and incidents
  • Managing day-to-day IT operations

But MSPs aren’t built for:

  • Executive-level strategy and prioritization
  • Business-aligned technology roadmapping
  • Independent evaluation of options and vendors

Even the strongest MSPs are typically reactive by nature—responding to requests, incidents, and defined scopes of work.
When they present options, leaders are often left with a critical question:
How do we objectively evaluate these choices in the context of our business goals?

How a Fractional CIO/CTO Helps

  • Provide business-aligned technology guidance
  • Evaluate vendor recommendations with an independent lens
  • Reduce risk by improving decision clarity and accountability
  • Act as an executive counterpart to MSPs, vendors, and internal teams

Unlike vendors who may benefit from specific tools or partnerships, a fractional executive is focused on
what is best for your organization—technically, financially, and operationally.

When a Fractional CIO or CTO Makes Sense

Organizations often seek fractional leadership during moments of change or complexity, such as:


Rapid growth or expansion

Your IT team is keeping systems operational, but strategic initiatives, scalability planning, and future-state architecture are difficult to prioritize.


High-stakes technology decisions

The executive team has defined objectives but lacks confidence in evaluating vendors, platforms, or architectural approaches.


Leadership gaps or transitions

You’ve lost a key IT leader and need experienced guidance to stabilize operations and chart a path forward.


Outsourced IT with unclear alignment

Your MSP may be performing well—or struggling—but you need assurance their recommendations and priorities align with your business strategy.

In each of these scenarios, a fractional CIO or CTO brings clarity, structure, and executive-level accountability—without the cost or commitment of a full-time hire.

The Value of Fractional Leadership

Fractional CIOs and CTOs are not a replacement for your internal team or service providers. They add a strategic layer—
connecting business goals to technology execution, reducing risk, and helping leadership teams make informed decisions with confidence.

The difference is moving from reacting to technology challenges to using technology as a competitive advantage.

Next step

Want to explore a fractional engagement?
Schedule a conversation with an expert


Tags: Fractional CIO, Fractional CTO, IT Strategy, Technology Leadership, MSP Oversight

Read more
  • Published in Technology
No Comments

AI Markdown Feed – A WordPress Plugin

Wednesday, 24 December 2025 by oit-wpadmin

AI Markdown Feed – A WordPress Plugin

AI Markdown Feed - Turn Website Content into AI-Friendly Format

Following a read of a post by Nicholas Khami, I decided it would be really nice to do something like this with a WordPress plugin. After a quick search of the WordPress plugin repository, I couldn’t see anything that would fit the bill. The basic concept is to deliver the basic structure from your site with a lower token count and less wasted context.

Purpose:

Provide a simple way to make your website more AI consumption-friendly with a turnkey WordPress plugin. Activate and make sure your agents consume the site with Accept: text/markdown header.

Implementation:

Since I’ve been developing software for a while now, I’ve been a relatively slow adopter of AI. Other than some auto-complete with Copilot and the like, I haven’t really embraced AI development. This seemed like a good project to feed through Claude Code. After having started a few project scaffolds with Claude Code, I decided I needed some structure here and used OpenSpec to walk me through the process. My first version worked, but was delivering too much information. I made some adjustments to the whitespace handling directly. I also had it re-work so we only worked with the main content body.

When:

I plan to be working toward getting this into the WordPress plugin repository at the beginning of January 2026. I’ve built quite a few private plugins for WordPress, but this will be the first one I’m releasing publicly. If you have an immediate need for this plugin, I can send you a link to an installable zip file if you reach out to me here.

References:


  • https://www.skeptrune.com/posts/use-the-accept-header-to-serve-markdown-instead-of-html-to-llms

  • https://github.com/Fission-AI/OpenSpec
Read more
  • Published in Technology
No Comments

When the Office Door Is Closed, Is Your Business Still Open?

Friday, 19 December 2025 by oit-wpadmin

When the Office Door Is Closed, Is Your Business Still Open?

You arrive at the office tomorrow morning only to find a notice from the city:
Entrance not permitted.
A foundation issue. A ruptured utility line. Something unexpected — and completely out of your control.

Someone physically stops you from entering.

What happens next?

Do you pivot immediately and keep operating, or does the day grind to a halt?
What if the disruption lasts a week? What if it’s longer?
Who decides the next step, and how quickly?

For some organizations, this scenario is an inconvenience. For others, it’s a full stop.

If your team can work securely from anywhere, access systems remotely, and continue serving customers without missing a beat,
that’s a sign of preparation. If not, the absence of a clear plan can quickly turn a temporary disruption into a material business risk.

This is exactly where Business Continuity Planning (BCP) proves its value.
BCP doesn’t have to be overly complex or theoretical. At its core, it’s about knowing — before something goes wrong —
what your next move is. Sometimes that’s a simple, one-page plan. Other times, it’s a structured decision framework that accounts
for multiple failure scenarios.

Either way, being prepared makes the difference between reacting under pressure and operating with confidence.


How We Help Organizations Prepare for the Unexpected

Business Continuity Cycle

  • Right-sized BCP development
    From lightweight, executive-ready continuity plans to comprehensive, multi-path decision models.
  • Technology-enabled continuity
    Assessing systems, access, and dependencies to ensure teams can operate securely from anywhere.
  • Scenario planning & risk analysis
    Identifying realistic disruption scenarios — not just worst cases — and defining clear response actions.
  • Clear ownership & decision frameworks
    Ensuring everyone knows who decides what and when during a disruption.
  • Practical, usable documentation
    Plans designed to be followed in real situations, not left on a shelf.

If you’re unsure what happens the next time your doors are closed — even temporarily — it may be time to put a business continuity plan in place.
Preparation today can protect tomorrow’s operations. Reach out for a consultation today.

Read more
  • Published in Technology
No Comments

Selling your business?

Friday, 12 December 2025 by oit-wpadmin

Preparing Your Business for Exit: How Smart Technology Increases Value Without Changing What Makes You Successful

For established business owners, the decision to transition toward retirement often starts with a simple question:
“How do I make this business attractive to the next owner—without breaking what already works?”

Technology Modernization  for Business Exit Summary Infographic

The answer increasingly lies in technology—but not in the way most founders fear.

This isn’t about ripping out familiar processes, forcing teams into generic tools, or chasing the latest software trends.
It’s about strategically modernizing the operational backbone so your business runs more efficiently,
more predictably, and with less owner dependency—while preserving the value proposition that made it successful.

Why Technology Matters in a Business Sale

Buyers and investors don’t just evaluate revenue and margins. They look closely at:

  • How dependent the business is on the current owner
  • How repeatable and documented core processes are
  • Whether operations can scale without adding headcount
  • How much “busy work” exists behind the scenes
  • The quality, reliability, and integration of internal systems

When a business relies heavily on manual work, spreadsheets, tribal knowledge, or the owner’s daily involvement, it introduces risk.
Risk lowers valuation.

Modern, well-designed systems do the opposite: they signal maturity, stability, and future upside.

The Real Goal: Reduce Operational Friction, Not Reinvent the Business

One of the biggest mistakes owners make when preparing for an exit is assuming technology means change—for customers, staff, or core workflows.

In reality, the most valuable improvements are often invisible externally.

The goal is to:

  • Minimize repetitive, manual tasks
  • Automate handoffs between departments
  • Improve visibility into operations and performance
  • Ensure the business can run smoothly without constant oversight

All without compromising how the product or service is delivered today.

Your customers shouldn’t notice a difference.
Your team should feel relief—not disruption.
And a future owner should see a business that “just works.”

Automations That Buyers Love (and Owners Appreciate)

Strategic automation removes low-value work from daily operations, freeing time and reducing errors. Common high-impact areas include:

  • Order or job intake workflows
  • Scheduling and resource allocation
  • Invoicing, billing, and payment processing
  • Reporting and performance tracking
  • Customer communications and status updates

The result is a business that feels calmer, more predictable, and less dependent on heroics—something both owners and buyers value highly.

Process Improvement That Preserves Institutional Knowledge

Over time, many businesses evolve processes organically. What started as a simple workaround becomes “the way we do things,”
even if no one can fully explain why.

Before an exit, this creates risk.

Modernizing for sale often includes:

  • Mapping critical processes end-to-end
  • Removing unnecessary steps and handoffs
  • Embedding best practices directly into systems
  • Making workflows repeatable and documented

When processes live inside the system—not just in people’s heads—the business becomes far easier to transition.

Using the Right Systems—Not More Systems

Buyers are wary of tool sprawl: disconnected platforms, manual integrations, and systems that only one person understands.

Technology modernization for exit focuses on:

  • Choosing systems that align with how the business actually operates
  • Integrating tools so data flows automatically
  • Eliminating redundant software and shadow processes
  • Creating a clear, understandable technology landscape

Simplicity and clarity matter more than feature lists.

A Different Approach: Technology That Fits Your Business

One of the biggest frustrations owners face is being told to “change how you work” to fit a piece of software.

We take the opposite approach.

We build software and systems around the client’s real-world processes.
Not generic workflows. Not off-the-shelf assumptions.
But technology that reflects how value is actually delivered today.

This means:

  • Preserving what already differentiates the business
  • Supporting existing strengths instead of flattening them
  • Making operations easier without losing identity

For buyers, this translates into confidence.
For owners, it means improvement without disruption.

The Exit You’re Really Preparing For

Whether you plan to sell in two years or five, the work you do now has immediate benefits:

  • Less day-to-day busy work
  • More time out of the weeds
  • Better visibility into performance
  • A business that runs smoothly without constant involvement

And when the time comes to transition, you’re not selling potential—you’re selling a
well-engineered operation built for continuity and growth.

Thinking about retirement or a future exit?

Modernizing your technology doesn’t have to mean changing your business. When done correctly, it makes what you’ve already built
easier to run, easier to understand, and far more attractive to the next owner.

Request a Free Evaluation

Read more
  • Published in Technology
No Comments

Should You Let AI Automate Everything?

Saturday, 06 December 2025 by oit-wpadmin

Should You Let AI Automate Everything?

AI tools are astonishingly capable. They can summarize documents, draft emails, classify data, and even hold basic conversations. It’s natural to ask: “If AI is this powerful, shouldn’t we just use it to automate everything?”

Programmatic Workflows, AI Components and Humans working together

In practice, the answer is no.
Relying on AI for every automation is a fast way to create fragile systems, inconsistent results, and frustrated teams.
The most reliable, efficient automation strategies use a blend of:
programmatic workflows, AI-driven steps, and human judgment.

AI Is Powerful – But It’s Not Your Whole Automation Strategy

AI is probabilistic, not deterministic. It predicts what is likely to be correct; it does not follow strict rules the way traditional software does. That means it’s fantastic for pattern recognition and language tasks, but risky when you need exact rules, precise calculations, or guaranteed outcomes.

When teams try to “let AI handle it all,” they often run into issues such as:

  • Integration friction: Difficulty connecting AI tools securely to CRMs, ERPs, accounting systems, and other data sources.
  • Workflow gaps: Low-code tools (e.g., Zapier-style systems) that don’t map cleanly to how the business actually operates.
  • Approximate answers where exactness is required: AI outputs that are “close enough” but still wrong in ways that matter (totals, dates, names, etc.).
  • Inconsistent behavior over time: The same prompt producing different results, making it hard to trust or troubleshoot.
  • Limited auditability: Difficulty answering, “Why did it do that?” when something goes wrong.

The key is recognizing where AI adds unique value and where traditional programmatic automation or humans should remain in control.

The Right Mix: Programmatic Workflows, AI, and Humans

We encourage clients to think of automation as a layered system:

  • Programmatic workflows: The backbone. Deterministic, rules-based logic that is predictable and testable.
  • AI components: Specialized “assistants” that handle judgment calls, language, and unstructured data.
  • Humans: Final authority on exceptions, high-risk decisions, and relationship-driven interactions.

When these three layers are designed together, you get systems that are both powerful and trustworthy.

When to Use Programmatic Workflows

Programmatic (rules-based) workflows are ideal when you need repeatable, predictable behavior. Use them when:

  • Steps are well defined: The process follows a clear, repeatable sequence (e.g., “if X, then do Y”).
  • No judgment calls are needed: The right answer can be written as a rule, not a “gut feeling.”
  • Systems expose APIs or import/export options: CRMs, accounting systems, databases, and other tools can be reliably integrated.
  • Tasks are high importance or high risk: Compliance processes, financial postings, critical notifications, and system-of-record changes.
  • You need audit trails: Being able to see exactly what happened, when, and why.

Example: Syncing customer data between your CRM and billing system, validating invoice totals, or enforcing approval rules before an order is released. These are best handled with traditional automation, not AI prompts.

When to Use AI Workflows

AI shines where structure breaks down and judgment is needed at scale. Use AI when:

  • Programmatic logic hits a wall: The task cannot be expressed as simple rules without becoming overly complex.
  • Minor judgment calls are acceptable on low to medium importance tasks: Classifying support requests, suggesting responses, summarizing conversations.
  • Interfacing with unknown people or systems: Parsing inbound emails from prospects, reading attachments, or interacting with other AI systems.
  • Processing large volumes of unstructured data: Emails, PDFs, free-form notes, and documents that would be expensive to handle manually.

Example: AI can read a long client email, classify its urgency and topic, draft a suggested response, and route it into the correct queue.
Programmatic logic then takes over to enforce SLAs, track status, and ensure follow-through.

When to Keep Humans in the Loop

Even with strong AI and automation, humans remain critical to a robust system. Use human steps when:

  • Both AI and programmatic workflows have demonstrated failure: Repeated edge cases, complex exceptions, or high-stakes decisions.
  • Specific approvals are required: Signing off on discounts, contract terms, compliance-sensitive steps, or unusual financial entries.
  • Client experience depends on human touch: Difficult conversations, strategic planning, and relationship-driven sales or service.
  • Prototyping new workflows: Let humans run the process manually first so you can validate the steps before codifying them with automation and AI.

The goal isn’t to remove humans entirely, but to reserve their time for the highest-value decisions and interactions.

Common Pitfalls When Teams Go “AI-First”

When organizations try to automate “with AI everywhere,” we often see patterns like:

  • Over-automation of unclear processes: Automating a broken workflow just lets you make mistakes faster.
  • No clear boundaries: AI is allowed to change critical data or trigger actions without guardrails.
  • Lack of monitoring and review: Nobody is regularly checking whether the AI is still performing as intended.
  • Underinvestment in basic plumbing: APIs, structured data, and well-designed workflows are ignored because “the AI will figure it out.”

The result is often more chaos, not less. The better approach is to:
use AI thoughtfully inside a well-designed automation architecture.

How Open InfoTech Solutions Helps

At Open InfoTech Solutions, we help companies design automation strategies that balance programmatic workflows, AI, and human oversight so you get:

  • Reliability: Core processes that run the same way every time, with clear logs and audit trails.
  • Intelligence where it counts: AI placed at specific points in the process to handle language, classification, and unstructured data.
  • Human control for critical decisions: Well-defined checkpoints where people review and approve exceptions or high-impact actions.
  • Better visibility: Dashboards and reporting to see what’s automated, what AI is doing, and where humans are required.

We don’t just plug in tools. We work with you to:

  • Map your existing workflows and identify automation opportunities.
  • Decide which steps should be rules-based, AI-driven, or human-driven.
  • Implement and integrate the right tools (including AI) into your systems securely.
  • Set up monitoring, exception handling, and continuous improvement routines.

Ready to Build Smarter Automations?

If you’ve tried to “let AI automate everything” and ended up with unreliable workflows or confusing results, you’re not alone. A better path is available.

Open InfoTech Solutions can help you design automations that are stable, scalable, and intelligent – without handing the keys to AI alone. If you’d like to review a specific workflow or explore where AI fits into your automation roadmap, please reach out to our team and let’s start the conversation. Contact Us

Read more
  • Published in Technology
No Comments

Can I work now? Anti-pattern

Tuesday, 19 March 2024 by oit-wpadmin

An anti-pattern is a design pattern discouraged for a variety of reasons. Regularly used in software development, anti-patterns are methods of accomplishing certain behavior which might be poorly implemented for either convenience or cost efficiency.

The reason I am drawing this terminology into some basic computerized businesses processes is because it is a good description of some of the issues I see with proper information flow inside of companies.

Today, I would like to highlight the “Can I work now?” anti-pattern. This immerges in a few places and usually associated with different processes. The basic circumstances look like this, the office is working on a document as a group in their individual workstations. You are ready to make your updates, but you cannot because someone is editing at the moment. So now you must call around the office and ask “Are you working on X? Could you please logout. I have something to add, which will take just five minutes.” It’s even more difficult if working remotely.

You may get lucky and easily identify who is working on what you need, other times it could be any number of people using this. Sadly, this is also the best-case scenario. At times a computer may crash and the file is locked without anyone actually using it. Other times, someone may be on vacation or even terminated from the company and it is still sitting open on their workstation without anyone knowing.

You can see how this can be frustrating and create a giant traffic jam in any business process.

These processes are used in:

  • Simple data collection built around Microsoft Excel (or similar spreadsheet software) programs.
  • Process, Walkthroughs, and Procedure Documentation.

Some reasons businesses are stuck with this model:

  • Older software.
  • Compliance is easier on an internal network than a cloud system.
  • Systems that are multi-user but because it slightly lowers a recurring cost, only one “license” is purchased for the system.
  • Older database systems that are multi-user BUT for whatever reason they are improperly configured and only allow one person in at a time, or worse, whenever multiple people are in it causes lost data that has led users to avoid using it at the same time.

Some solutions to this problem:

  1. Migrating to a cloud platform
    • Google Sheets
    • Microsoft SharePoint/OneDrive on Microsoft 365
    • Airtables provides a cloud based highly flexible spreadsheet system with a lot of database-like capabilities and custom programming.
  2. Build dashboards to replace manual entry that maintain themselves and are less likely to human error.
  3. Build custom software to meet needs precisely.

This software may continue to function with existing software or stand alone as a complete replacement.

Read more
  • Published in Technology
No Comments

© 2025 Open InfoTech Solutions, All rights reserved.

TOP