<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent &amp; Upcoming Talks | Giulia Solinas</title><link>https://giuliasolinas.github.io/events/</link><atom:link href="https://giuliasolinas.github.io/events/index.xml" rel="self" type="application/rss+xml"/><description>Recent &amp; Upcoming Talks</description><generator>Hugo Blox Builder (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Wed, 08 Oct 2025 07:30:00 +0000</lastBuildDate><image><url>https://giuliasolinas.github.io/media/icon_hu_982c5d63a71b2961.png</url><title>Recent &amp; Upcoming Talks</title><link>https://giuliasolinas.github.io/events/</link></image><item><title>Hybrid Platform: A Panel at IBM TechXchange 2025</title><link>https://giuliasolinas.github.io/events/hybrid_platform_txc/</link><pubDate>Wed, 08 Oct 2025 07:30:00 +0000</pubDate><guid>https://giuliasolinas.github.io/events/hybrid_platform_txc/</guid><description>&lt;h2 id="from-silos-to-seamless-flow--building-hybrid-workflows-that-scale"&gt;From Silos to Seamless Flow – Building Hybrid Workflows That Scale&lt;/h2&gt;
&lt;h3 id="a-personal-note"&gt;A Personal Note&lt;/h3&gt;
&lt;p&gt;I was honored to &lt;strong&gt;moderate the IBM TechXchange 2025 Peer Roundtable&lt;/strong&gt; titled &lt;em&gt;“Building Seamless Workflows Across Hybrid Environments.”&lt;/em&gt; As an &lt;strong&gt;AI consultant&lt;/strong&gt; and IBM champion I had the pleasure of moderating the conversation, fielding questions, and helping the participants surface practical patterns for integrating on‑prem, cloud, and edge resources into a single, reliable workflow.&lt;/p&gt;
&lt;p&gt;My partners in crime were Chris Backer, Madhu Kochar, Steven Perva, and Sarah Julia Kriesch.&lt;/p&gt;
&lt;p&gt;Below you’ll find a concise recap of the roundtable insights, followed by a deeper dive into the lessons learned and actionable tactics you can start using today.&lt;/p&gt;
&lt;h2 id="-quicktake-summary-of-the-roundtable"&gt;📊 Quick‑Take Summary of the Roundtable&lt;/h2&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;strong&gt;What We Explored&lt;/strong&gt;&lt;/th&gt;
&lt;th&gt;&lt;strong&gt;Why It Matters&lt;/strong&gt;&lt;/th&gt;
&lt;th&gt;&lt;strong&gt;Key Take‑aways for Practitioners&lt;/strong&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Connecting disparate tools &amp;amp; platforms&lt;/strong&gt; (on‑prem, cloud, edge)&lt;/td&gt;
&lt;td&gt;Breaks silos, reduces manual hand‑offs, unlocks automation.&lt;/td&gt;
&lt;td&gt;• Create a &lt;strong&gt;single source of truth&lt;/strong&gt; inventory of services.&lt;br&gt;• Adopt &lt;strong&gt;API‑first&lt;/strong&gt; integration layers.&lt;br&gt;• Use &lt;strong&gt;event‑driven patterns&lt;/strong&gt; (Kafka, IBM Event Streams) for real‑time data flow.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Common setbacks&lt;/strong&gt; (inconsistent APIs, latency spikes, vendor lock‑in)&lt;/td&gt;
&lt;td&gt;Project delays, higher TCO, unpredictable performance.&lt;/td&gt;
&lt;td&gt;• Implement &lt;strong&gt;contract testing&lt;/strong&gt; early.&lt;br&gt;• Apply &lt;strong&gt;observability stacks&lt;/strong&gt; (Prometheus, IBM Observability by Instana).&lt;br&gt;• Prefer &lt;strong&gt;containerized, stateless services&lt;/strong&gt; to mitigate lock‑in.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Security &amp;amp; visibility&lt;/strong&gt; across hybrid landscapes&lt;/td&gt;
&lt;td&gt;A breach in one domain can cascade; lack of visibility stalls troubleshooting.&lt;/td&gt;
&lt;td&gt;• Deploy &lt;strong&gt;Zero‑Trust networking&lt;/strong&gt; and micro‑segmentation.&lt;br&gt;• Centralize &lt;strong&gt;IAM&lt;/strong&gt;.&lt;br&gt;• Unified logging/SIEM (IBM QRadar) for cross‑environment correlation.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Regulatory &amp;amp; governance pressures&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Uncertainty can freeze innovation; clear guidance can accelerate road‑maps.&lt;/td&gt;
&lt;td&gt;• Adopt &lt;strong&gt;policy‑as‑code&lt;/strong&gt;.&lt;br&gt;• Map regulations to concrete &lt;strong&gt;data‑flow controls&lt;/strong&gt; and automation rules.&lt;br&gt;• Leverage &lt;strong&gt;AI‑driven compliance dashboards&lt;/strong&gt; for proactive risk detection.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;AI‑enhanced workflows&lt;/strong&gt; (e.g.,with Maximo and IBM watsonx)&lt;/td&gt;
&lt;td&gt;Turn data into actionable insight, speed decision‑making, cut manual effort.&lt;/td&gt;
&lt;td&gt;• Use a &lt;strong&gt;data‑fabric&lt;/strong&gt; platform to feed trusted AI models.&lt;br&gt;• Start with low‑risk use cases—predictive maintenance, anomaly detection—and expand as confidence grows.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="1-why-hybrid-integration-is-no-longer-optional"&gt;1️⃣ Why Hybrid Integration Is No Longer Optional&lt;/h2&gt;
&lt;p&gt;Modern enterprises run on a patchwork of &lt;strong&gt;on‑premises servers, public clouds, and edge devices&lt;/strong&gt;. When each environment speaks its own language, moving data becomes costly and error‑prone. The roundtable showed that the first step toward a unified workflow is &lt;strong&gt;visibility&lt;/strong&gt;: catalogue every endpoint, map its data contracts, and treat every interaction as a first‑class API.&lt;/p&gt;
&lt;blockquote class="border-l-4 border-neutral-300 dark:border-neutral-600 pl-4 italic text-neutral-600 dark:text-neutral-400 my-6"&gt;
&lt;p&gt;&lt;strong&gt;Takeaway:&lt;/strong&gt; &lt;em&gt;A single source of truth for services and contracts eliminates unexpected breakages downstream.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="2-common-pitfalls--how-to-dodge-them"&gt;2️⃣ Common Pitfalls &amp;amp; How to Dodge Them&lt;/h2&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Pitfall&lt;/th&gt;
&lt;th&gt;Real‑world Symptom&lt;/th&gt;
&lt;th&gt;Remedy (from the discussion)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Inconsistent API contracts&lt;/td&gt;
&lt;td&gt;“The integration failed because the vendor changed the schema overnight.”&lt;/td&gt;
&lt;td&gt;Adopt &lt;strong&gt;contract testing&lt;/strong&gt; and versioned API gateways.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Latency spikes in cross‑cloud calls&lt;/td&gt;
&lt;td&gt;“Requests take &amp;gt;5 s when hitting an external SaaS.”&lt;/td&gt;
&lt;td&gt;Move to &lt;strong&gt;event‑driven architectures&lt;/strong&gt; and place compute closer to the data source (edge).&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Security blind spots&lt;/td&gt;
&lt;td&gt;“We discovered a compromised edge node weeks later.”&lt;/td&gt;
&lt;td&gt;Implement &lt;strong&gt;Zero‑Trust&lt;/strong&gt; policies and unify logging with SIEM.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Regulatory uncertainty&lt;/td&gt;
&lt;td&gt;“New data‑localization rules forced us to halt a migration.”&lt;/td&gt;
&lt;td&gt;Use &lt;strong&gt;policy‑as‑code&lt;/strong&gt; and AI‑enabled compliance dashboards to pre‑emptively adapt.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;hr&gt;
&lt;h2 id="3-the-role-of-ai-in-making-workflows-smart"&gt;3️⃣ The Role of AI in Making Workflows “Smart”&lt;/h2&gt;
&lt;p&gt;AI isn’t a silver bullet, but it &lt;strong&gt;turns data into insight&lt;/strong&gt; that can automate decisions. Participants highlighted three practical entry points, one of which directly ties to the public administration and from the application of Maximo to predictive maintenance:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Predictive Maintenance&lt;/strong&gt; – Using sensor streams from edge devices to trigger pre‑emptive service calls.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Anomaly Detection&lt;/strong&gt; – Feeding unified logs into a machine learning model that flags out‑of‑pattern behavior before it becomes an outage.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Workflow Optimisation&lt;/strong&gt; – Recommending the next best step in an automation chain (e.g., “run job X before job Y”) based on historical success rates.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="4-governancespeed-managing-regulatory-constraints"&gt;4️⃣ Governance + Speed: Managing Regulatory Constraints&lt;/h2&gt;
&lt;p&gt;Regulators often feel like moving finish lines. The conversation on the regulatory hurdles kept was vivid. The roundtable consensus was:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Policy‑as‑Code&lt;/strong&gt; turns abstract rules into executable checks that run automatically in CI/CD pipelines.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Unified Governance Platforms&lt;/strong&gt; (for example, watsonx Governance for AI models) provide a single pane of glass for data‑location, retention, and access policies.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;AI‑assisted compliance&lt;/strong&gt; can surface the most urgent gaps, allowing teams to pause or accelerate projects &lt;em&gt;with data‑backed justification&lt;/em&gt; rather than guesswork.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id="5-blueprint-for-a-seamless-workflow-initiative"&gt;5️⃣ Blueprint for a “Seamless Workflow” Initiative&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Discover &amp;amp; Map&lt;/strong&gt; – Catalogue every system, data source, and integration point.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Standardize Contracts&lt;/strong&gt; – Define OpenAPI specs, versioning rules, and test contracts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Build Observability&lt;/strong&gt; – Deploy metrics, tracing, and logs that span environments.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Secure the Path&lt;/strong&gt; – Apply micro‑segmentation, IAM federation, and data‑masking where needed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Layer AI Incrementally&lt;/strong&gt; – Choose a pilot use case (e.g., the email‑reply automation), train models on trusted data, and monitor ROI.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Govern &amp;amp; Iterate&lt;/strong&gt; – Use policy‑as‑code to keep compliance baked into every release.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="6-closing-thought"&gt;6️⃣ Closing Thought&lt;/h2&gt;
&lt;p&gt;The roundtable proved that &lt;strong&gt;speed and safety are not opposites&lt;/strong&gt;—they become allies when you design integration with visibility, automation, and governance baked in from day one. By treating hybrid environments as a single, programmable fabric, organizations can unlock the agility needed to compete in today’s data‑driven market.&lt;/p&gt;
&lt;hr&gt;</description></item><item><title>Digital Strategizing</title><link>https://giuliasolinas.github.io/events/digital-strategizing/</link><pubDate>Sat, 01 Aug 2020 13:00:00 +0000</pubDate><guid>https://giuliasolinas.github.io/events/digital-strategizing/</guid><description>&lt;p&gt;In summer 2020, I had the pleasure of co-chairing a PDW session at the during the &lt;strong&gt;Academy of Management Conference&lt;/strong&gt;, together with
,
. The podium discussion covered the role of &lt;strong&gt;digitization in strategizing&lt;/strong&gt; with a panel of experts.&lt;/p&gt;
&lt;p&gt;What is the matter? Digital technologies such as platforms, big data analytics, and algorithms are reshaping how firms strategize. A first effect is &lt;strong&gt;altering the strategy-making process&lt;/strong&gt;, which has become less exclusive and secret, and more flexible. Second, digital technologies are also &lt;strong&gt;redefining strategy-making practices&lt;/strong&gt;, allowing actors to participate from afar or utilizing the wisdom of the crowd.&lt;/p&gt;
&lt;p&gt;We discussed these two effects, their significance for business, and their influence on the strategic management research agenda.&lt;/p&gt;
&lt;p&gt;Who was be &amp;ldquo;on the stage&amp;rdquo; with us? &lt;strong&gt;Stefan Haefliger&lt;/strong&gt; (Cass Business School, UK) &lt;strong&gt;Julia Hautz&lt;/strong&gt; (U. of Innsbruck, AUT), &lt;strong&gt;Ann Majchrzak&lt;/strong&gt; (U. of Southern California, USA), &lt;strong&gt;Stella Pachidi&lt;/strong&gt; (U. of Cambridge, UK), &lt;strong&gt;Sotirios Paroutis&lt;/strong&gt; (Warwick Business School, UK), &lt;strong&gt;Richard Whittington&lt;/strong&gt; (U. of Oxford, UK).&lt;/p&gt;
&lt;div class="callout flex px-4 py-3 mb-6 rounded-md border-l-4 bg-blue-100 dark:bg-blue-900 border-blue-500"
data-callout="note"
data-callout-metadata=""&gt;
&lt;span class="callout-icon pr-3 pt-1 text-blue-600 dark:text-blue-300"&gt;
&lt;svg height="24" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"&gt;&lt;path fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m16.862 4.487l1.687-1.688a1.875 1.875 0 1 1 2.652 2.652L6.832 19.82a4.5 4.5 0 0 1-1.897 1.13l-2.685.8l.8-2.685a4.5 4.5 0 0 1 1.13-1.897zm0 0L19.5 7.125"/&gt;&lt;/svg&gt;
&lt;/span&gt;
&lt;div class="callout-content dark:text-neutral-300"&gt;
&lt;div class="callout-title font-semibold mb-1"&gt;Note&lt;/div&gt;
&lt;div class="callout-body"&gt;&lt;p&gt;This content is part of my academic stint. However, a practice perspective is essential in my daily routine in the IT sector, where I am asked to combine both technical insights with business acumen.&lt;/p&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;Interested readers can check the
.&lt;/p&gt;</description></item></channel></rss>