How would you use data analytics to identify bottlenecks in your business architecture processes?

Desde mi experiencia, el análisis de datos es fundamental para mejorar los procesos del negocio. Sin embargo, una de las principales fallas está en identificar cómo medir. Para tener datos fiables es imperante identificar: - El "sujeto de control" -Los métodos e instrumentos de medición Adicionalmente asegurar la fiabilidad de las mediciones. - Instrumentos - Personas Cuando hablamos del sujeto de control, muchas veces nos centramos en medir un resultado. Yo sugiero, identificar los factores que afectan los resultados y medirlos.

The very first thing you want to do, is DEFINE the problem; then decide if analytics are even a feasible solution to the problem. If so, then you'll want to make sure that you collect the right data AND that you understand the data... sometimes data fields aren't named intuitively, or can mean different things in different contexts. As far as patterns, TSAF (time series analysis and forecasting) often helps; these can uncover whether your bottlenecks are seasonal or time-sensitive (perhaps you are operating in North America E.S.T., and the bottleneck occurs around 2pm your time). For causes, I would try to separate them into endogenous and exogenous categories (to use terms from economic models)

Data gathering in EA is akin to implementing comprehensive system logging across your enterprise. Develop an "Architectural Telemetry Framework" that collects data from various touchpoints in your business processes. Think of it as setting up distributed tracing in a microservices architecture, but for your entire business workflow.

Usually it depends on where the data is residing, if there is a core ERP or data lake, getting the biz process data could be much simpler.

My goto methodology for SAP customer base is to use SAP signavio, it can connect to existing ERP and provide ready data, red line potential problems, provide industry benchmarks and recommend corrective action as well as solution capabilities to leverage.

Communication with biz stakeholders is the key. Providing a safe environment to talk about leaving the inter department issues aside is very important. People should see what's in it for me.

Apply root cause analysis within the context of your architectural layers. Imagine yourself as a detective in an architectural mystery - trace the "clues" (data anomalies) through different "scenes" (architectural components) to uncover the true "culprit" (root cause) behind each bottleneck.

Develop a transformation roadmap based on your target architecture state. Picture yourself as an architectural engineer - design "bypass routes" (process improvements) and "expansion projects" (capability enhancements) that will alleviate congestion points, ensuring smooth "traffic flow" (business operations) across your enterprise landscape.

Establish a continuous architecture assessment framework linked to key performance indicators. Think of it as setting up an architectural "mission control" - create dashboards that provide real-time insights into your solutions' effectiveness, allowing for agile adjustments to maintain optimal "system performance" (business efficiency).