Quote for the day:
"Listen with curiosity, speak with honesty act with integrity." -- Roy Bennett
🎧 Listen to the audio debrief on YouTube
▶ Play Audio DigestDuration: 20 mins • Perfect for listening on the go.
How to level up from IT management to IT leadership
Transitioning from a mid-level technical management position to a senior
executive role requires a deliberate shift in focus from mastering technology
to mastering human connections and business operations. Aspiring leaders must
build upon their foundational knowledge by developing essential communication
habits, such as empathy, active listening, and the ability to build trust
across different departments. Successfully navigating this career path
involves taking on significant projects, learning from the inevitable
missteps, and seeking out experienced mentors who can provide honest feedback.
It is crucial to understand the broader goals of the organization and how
technology can practically support those objectives. This means stepping away
from the desk to learn about budgeting, risk management, and the daily
challenges faced by other teams. True leadership is not defined by a specific
title, but by the capacity to align people around a shared vision and empower
them to succeed. Rather than simply executing technical tasks, effective
leaders focus on mentoring their teams, translating complex concepts into
plain language for non-technical coworkers, and making thoughtful decisions
that deliver measurable value. Ultimately, ascending to the executive level is
about solving company-wide problems with calm confidence and a steady
collaborative mindset.Why IoT systems fail at scale – and why Edge vs Cloud is the wrong debate
Internet of Things systems often struggle to scale, but the root cause is
rarely the technology itself. Instead, failures usually stem from fragmented
design. When teams develop hardware, software, connectivity, and security in
isolation, the gaps between these components become major hurdles once the
system moves into production. The ongoing debate pitting edge computing
against the cloud misses the point. In practice, successful systems rely on
both. The real challenge lies in deciding how they work together—specifically,
figuring out which data should be processed locally for quick, time-sensitive
tasks and which should be sent to the cloud for long-term analysis. This need
for unified design is becoming even more obvious as artificial intelligence
enters the picture. AI requires clear, reliable data pipelines. If a system's
architecture is disjointed, having massive amounts of data won't help much. To
build systems that last, developers need to shift from component-level
thinking to holistic system design. This means planning data flow, security
protocols, and long-term maintenance strategies from the very beginning.
Treating features like security or software updates as add-ons only creates
expensive problems later. By building a cohesive architecture from day one,
organizations can create reliable systems that easily adapt and grow over
time.The new audit equation puts AI to work and judgement at the centre
In a recent interview, Atul Deshmukh of the accounting firm KNAV discusses how
artificial intelligence is transforming the auditing profession from the
ground up. Central to this shift is the transition from traditional
statistical sampling to the comprehensive analysis of entire data sets. By
deploying AI platforms, firms can automate repetitive and time-consuming tasks
like document extraction and transaction matching. These digital workers
drastically compress the time required for routine procedures, turning tasks
that once took a full day into minutes. This efficiency is fundamentally
altering the traditional accounting firm structure. The classic pyramid model,
which relied heavily on junior staff for groundwork, is evolving into a
diamond shape that demands analytical thinking and diverse backgrounds,
including engineering. Furthermore, the massive time savings challenge the
industry's conventional billable-hour model, paving the way for pricing based
on value, complexity, and outcomes. Despite AI taking on larger segments of
the workflow and even moving toward autonomous processes, human judgment
remains the irreplaceable core of auditing. Auditors are not being replaced;
their roles are shifting from manual verification to higher-level review and
critical decision-making. Ultimately, AI handles the heavy lifting, allowing
human professionals to focus their time on complex analysis and valuable
insights.
What the CISO role will look like in 2029
By 2029, the role of the Chief Information Security Officer will shift away
from being a purely technical position focused on building network defenses.
Instead, security leaders will take on broader responsibilities as business
strategists and risk managers. As technology cycles shorten and artificial
intelligence accelerates the pace of both innovation and cyber threats, the
old approach of simply saying no to all new ideas will no longer work.
Tomorrow’s security executives will be expected to help their organizations
take smart, calculated risks. Rather than managing security tools in
isolation, future leaders will act as organizational orchestrators. They will
connect engineering, legal, product, and executive teams to build systems that
can identify and reduce risks almost instantly. Because threats are moving
faster, organizations will rely on resilient engineering and automated
decision-making processes to maintain safety. Some experts predict that the
position will even expand to cover overall enterprise risk, potentially
changing titles to emphasize trust and broader risk management. Despite these
changes, the fundamental mission of the job remains steady. Security leaders
will still need strong technical foundations, sound judgment, and clear
communication skills to protect the entire business and help executives make
informed choices in a rapidly changing world.The Infrastructure Bottleneck That Keeps AI From Scaling Up
While many organizations focus entirely on choosing the right artificial
intelligence models, the real challenge in making these systems work at a
large scale lies in the underlying physical and technical foundational
structures. According to Dilip Kumar of NTT DATA, practically all
organizations find that their current networks, data storage, and security
setups are slowing down their progress. Proving that an AI tool works in a
small initial test is relatively simple, but running it reliably across an
entire business is much harder. A common mistake is buying thousands of
expensive software licenses without having the internal systems to actually
use them. It is similar to buying a high-performance sports car but having no
paved roads to drive it on. For AI to be truly useful, companies must ensure
their networks can handle the data traffic and that their information is clean
and organized. Instead of trying to transform an entire business at once, a
smarter approach is to focus on a single, specific problem. By ensuring the
foundation—the core networks, data organization, user identity, the
appropriately sized model, and the daily operating procedures—is solid,
businesses can prove the value of their investment quickly and then expand
those efforts with complete confidence.
The Rise of Runtime Governance
In the article "The Rise of Runtime Governance," Christian Siegers argues that
artificial intelligence forces a fundamental shift in how modern organizations
manage system behavior. Historically, enterprise governance focused heavily on
the implementation phase. Dedicated teams reviewed system architectures,
assessed security measures, and validated strict compliance standards well
before deployment. This approach was highly effective for traditional systems
because their behavior was largely dictated by static code and predefined
business rules. However, AI introduces a complex new dynamic where critical
decisions actually occur during execution. Even if an AI system successfully
passes all pre-deployment governance checks, its behavior can still drift due
to changing context, model interactions, and new information retrieval.
Consequently, companies may strictly follow governance processes without
actually retaining control over the final operational outcomes. To bridge this
gap, Siegers suggests that governance must evolve from a series of static
checkpoints into a continuous architectural capability. This concept, known as
runtime governance, requires embedding continuous system observability, active
policy enforcement, and human oversight directly into the daily operational
environment. By doing so, organizations can monitor what their systems are
doing in real time, ensure all behavior remains within acceptable boundaries,
and actively intervene when necessary. This ultimately maintains true control
over AI-enabled operations long after the initial deployment.Agentic Fitness Functions: Extending Evolutionary Architecture Beyond Deterministic Rules
/articles/agentic-fitness-functions-evolutionary-architecture/en/smallimage/thumbnail-1786428822427.jpg)
Evolutionary software architecture relies on fitness functions—automated
checks like dependency rules, performance budgets, and security scans—to
ensure systems can change safely over time without degrading their core
characteristics. While these deterministic rules are excellent for enforcing
strict, measurable metrics, they often fall short when evaluating complex,
judgment-heavy architectural concerns. For example, a basic schema check can
confirm that an application programming interface still functions, but it
cannot determine if a new field accidentally leaks user interface details into
a core domain model. This is where agentic fitness functions come into play to
fill the gap. By using artificial intelligence agents calibrated with past
architectural decisions, ownership data, and clear rubrics, these functions
can evaluate nuanced changes that defy simple yes-or-no rules. They are not
meant to replace human architects or traditional automated tests. Instead,
they act as an advisory layer that provides structured feedback, including
confidence scores and clear reasoning, for changes that require context and
human-like judgment. This approach helps teams maintain healthy system
boundaries, catch semantic drift early, and ensure that architectural intent
is preserved. Ultimately, agentic fitness functions make complex architectural
decisions more transparent and auditable, allowing teams to confidently manage
rapid software delivery and continuous system evolution.
From Agile to the Product Operating Model
Based on a recent survey of 48 practitioners, the transition from traditional development methods to a product operating model often changes company vocabulary and structure more than it changes how decisions are actually made. Among the respondents whose organizations are making this shift, most report that their teams still operate by building requested features rather than acting as fully empowered groups that decide how to solve problems. However, the survey does highlight some positive trends. Many participants notice improvements in the speed of delivery, the value provided to customers, and overall collaboration with stakeholders. On the other hand, business results remain largely inconclusive, likely because financial outcomes take longer to measure. One notable concern is the human element, as team morale and developer satisfaction appear to decline during these transitions. Additionally, the findings show that artificial intelligence adoption and structural operating changes are happening as separate efforts. While artificial intelligence is starting to influence how product decisions are made across many companies, this shift is occurring independently of formal organizational redesigns. Overall, the data suggests that while operational efficiency might improve, true changes in decision making authority and employee well being remain significant challenges for organizations attempting this transition today.US cloud act, sovereignty, and why you might need to care
The article by Kate Carruthers discusses the crucial difference between data
residency and true data sovereignty, emphasizing that physical location alone
does not insulate data from foreign legal reach. Prompted by Airbus’s decision
to move critical applications to a European provider, the piece highlights
that the US CLOUD Act allows US authorities to compel American cloud providers
to hand over data, regardless of whether that data is stored in Sydney,
Frankfurt, or Dublin. This makes cloud hosting a matter of national security
and governance, not just a technical or architectural choice. The author notes
that Australia often mistakenly equates local data residency with sovereignty,
creating a blind spot that leaves critical infrastructure vulnerable to
geopolitical disputes or commercial shifts. Organizations are advised to map
their vital dependencies and classify workloads based on the potential harm of
disruption rather than blindly adopting a "cloud-first" strategy. Furthermore,
companies should design systems for degraded operation, practice isolation
techniques, and preserve clear exit options to ensure resilience. Ultimately,
Carruthers argues that cloud computing has evolved into institutional and
geopolitical infrastructure, requiring boards to make deliberate, strategic
choices about where sensitive workloads sit and how much control they truly
retain.The cyber resilience divide
In today's digital landscape, security incidents are a routine reality, and
companies can no longer rely solely on preventing attacks. A recent Fujitsu
report explores the growing gap between organizations that successfully build
strong defenses and those that remain vulnerable, particularly as artificial
intelligence reshapes both security threats and defense strategies. While
artificial intelligence helps criminals find weaknesses and automate attacks,
it also provides companies with powerful tools to detect and respond to these
threats early. The research identifies a clear division between leading
organizations and those lagging behind. Leaders understand that security
breaches are inevitable. Rather than focusing only on prevention, they prepare
to maintain operations and recover quickly. They treat security as a shared
priority that begins at the board level, balancing new technology adoption
with careful oversight. By running practical simulations and using smart tools
for defense, these leaders reduce the impact of incidents while building trust
and supporting steady growth. In contrast, lagging organizations often rush to
adopt new technologies without fully understanding the risks, leaving gaps in
their defenses. To secure their futures, companies must accept that breaches
will happen, embed security awareness into their daily routines, and focus on
protecting their most important systems through practical testing.
