In complex software projects, success rarely comes from technical execution alone. Equally critical are the business insights that align solutions with organizational goals, workflows, and constraints. These two dimensions—technical and business acumen—often reside in different roles. Engineers typically own the technical depth; project managers or business analysts tend to carry the business perspective. But when these skill sets converge—whether in individuals or collaborative teams—projects gain the flexibility and foresight needed to navigate obstacles.
One SharePoint implementation I was involved in illustrates this dynamic.
The project encountered a serious roadblock: existing InfoPath form schemas, already deployed across the organization, were incompatible with the dynamic sections required for SharePoint integration. This incompatibility threatened the viability of the entire effort.
A dual-track approach proved effective. On the technical side, we identified that the core challenge lay in validation logic. By rewriting the field-level validation scripts to invert the original logic—essentially replacing dynamic expansion with conditionally triggered manual sections—we made the forms compatible without altering the underlying data structures.
On the business side, this technical workaround required a change in how forms were completed by end users. A revised procedure was proposed and vetted with stakeholders across departments to ensure feasibility and compliance.
Once the concept was proven technically and validated with users, the plan was presented to project sponsors. Approval was granted to extend the project timeline by one month and assign additional staff—three developers and two analysts—to complete the implementation. The revised approach allowed the SharePoint deployment to move forward successfully.
This example underscores a broader principle: many project roadblocks do not yield to technical solutions alone. Likewise, business workarounds often fail if the underlying systems cannot support them. It is at the intersection of these two perspectives that durable, practical solutions often emerge.
Think back on your own project experiences. What kinds of problems were solved not just by code or policy, but by a combination of both? Was the integration of technical and business thinking the result of a single person’s versatility, or of a team collaborating effectively across domains?
