Research and Development

SysLab specializes in improving operational productivity of information-centric work and innovates to design operational structures suited for work in the Information economy.

Unlike traditional operations management that mostly focuses on materials and manufacturing, our focus is in the realm of operations management that deals with data and knowledge-workers governed by business processes, digital devices, software applications and global work structures. As a pioneer in this area, Information-centric Operations, we publish research and collaborate with industry & academia to develop this emerging science.

We would soon update this page with our past and current research projects. For now, we hope that the following insights developed by our Research team will be of value in improving Execution of your Business Operation Initiatives.

Where do business process and business application initiatives fail?

A recent SysLab study reveals the following ten factors:

  • Highly driven by non-technical knowledge workers. Unless they adopt, irrespective of the elegance and benefits of a solution, the initiative fails.
  • Often no clear owner (eBusiness vs. Functional owners). Where would the budget come from?
  • No clear language for assessing the problem and trade-offs. Discussions and Assessments are often less objective in nature.
  • Abundant but under utilized data/IT infrastructure. communication gap and power differences between the business and technology communities often makes it hard to asses the case for re-usability.
  • Design for Execution. High failure rate and/or delays in initiatives are frequent. Though avoidable, often fuzzy-factors and infeasibilities are not given enough consideration during planning, and they bite-back with 10-fold intensity during execution. Don't just have a plan that's logical, coherent and convincing but ensure that it's well designed for Execution.


Silber Besteck

  • Rapid workplace dynamics # How long will the proposed solution be valid? Inappropriate consideration of the time element and its implications is a key contributor for resource waste and delays in Execution. # Having a roadmap of bite-sized execution with business value at each phase only appears a dream. Phased deliverables exist, but what's the use, if we can't realize the business value for 6-9 months of execution? More than one solution to a given problem is not uncommon. Also, a quick fix delivering reasonable business-value with start-to-finish execution in 3 months is always possible. So don't miss to at least identify such quick gains.
  • Failure to perform the reality test. What if, after all that effort its discovered that the solution so delivered doesn't provide the utility and value as desired? or perform as marketed? Especially when the initiatives have large scope, not many bother about such issues.
  • Behavioral effects are 50% of the game Strange it may seem, though all of us are professional enough, understanding the implications of the behavioral effects of all stakeholders, directly or indirectly effecting the project is key. Inappropriate management of this factor results in more emotional burden and often more stress and delays in execution, if not failure.
  • Let requirements drive action, not vice-versa. Business operation problems are often simple to understand. We noticed that in some initiatives, solutions were chosen based on just this understanding (as in, I have problems in managing customer interactions and customer data, so a CRM solution would be appropriate for my firm). However, though solutions are marketed to address our needs, Fick-Kontakte.info they actually automate the details which is where most mismatches are found during execution. As a fix, firms tried to alter their requirements to suit the solutions, but soon they experience resistance to change their own work-methods. Such experiences did happen even with matured software infrastructures like that of Oracle. To avoid such problems, irrespective of the project-size/scope, please do enough diligence Exender.com on requirements. In practice, we are finding a night and day difference in the execution-approach & budget to the same problem when requirements and expectations were appropriately developed and tested!!! before deciding on action.
Silber Besteck