ARKADIUSZ JANISZEWSKI

____________________________________________________________________________________________________________________________________________________________________

01. Context Injection

Context Engineering, not file upload.

The quality of the response depends on the purity of the data. Before

I run the process, I distill the documentation. I prepare Project DNA

in the form of dedicated Markdown files.

This allows me to remove the information noise and provide my assistants with only the essentials: the Contract and Standards (DNV) provisions, along with the nuances of the Scope of Work, Schedule, and Thought Journal.

The system receives strict guidelines, eliminating external information noise.

Project Scope

Thought Journal

Stakeholder Map

HSE & Regulations

Risk Assessment

Contract Terms

____________________________________________________________________________________________________________________________________________________________________

Anatomy of a Decision: SiteAI Chain

SiteAI Chain isn't a chatbot. It's an autonomous decision-making chain. See how raw data from the project

goes through 3 pillars of validation to become a ready-made strategy for the management board.

"You don't hire me for my memory. You hire me for my decisions".

Most managers use AI as a "search engine." I use it as an exoskeleton.

The diagram below represents my cognitive architecture.

SiteAI doesn't "guess".

It operates in a closed-loop verification system, moving from raw data (Input),

through orchestration of assistants (Process), to a final decision document (Output).

Here's how I turn information chaos into a "Strategic One Pager" in 4 steps:

Noise Elimination

Selecting Assistants

Recognizing Intentions

02. The Orchestrator

Autonomous Command.

SiteAI Chain takes on the role of a digital Chief of Staff. Its task is to accurately diagnose the challenge and select a "Strike Team" appropriate to the scale of the threat.

The system dynamically manages the competences of assistants, creating a dedicated decision-making chain for this one specific task - without unnecessary procedures and operational delays.

Od Chaosu

do Klarowności

W nowoczesnym zarządzaniu nie brakuje danych. Brakuje zrozumienia. Jesteśmy zalewani raportami, mailami i metrykami, a mimo to kluczowe decyzje wciąż podejmujemy w chaosie,

gasząc pożary zamiast budować systemy.

Nazywam się Arkadiusz Janiszewski. Po ponad dekadzie w okopach złożonych projektów zrozumiałem, że prawdziwa kontrola nie pochodzi z większej ilości danych, ale z ich głębszej syntezy z ludzką intuicją.

Ten blog to manifest tej filozofii. To zbiór dowodów i narzędzi, które pomogą Ci przestać walczyć z objawami i stać się architektem pełnego zrozumienia w Twoim zespole i projektach.

CZYTAJ WIĘCEJ

> CFO

The Margin & Liability Guard.

It is a financial "interceptor" that analyzes project operations through the lens of margin protection and claim security. In an industry where a single logistics error can cost a fortune, the CFO Assistant becomes your financial shield.

Key Engine Specifications:

Risk-Informed Financial Architecture: The system applies project financial management paradigms (including standards from the HBR Guide to Finance for Managers). The assistant's logic filters operational decisions based on their impact on cash flow and potential Liquidated Damages (LDs).

Liability Verification Logic: Every solution is verified against contractual rigors. The system identifies claim risks, before they materialize as losses.

Scenario Financial Stress-Testing: The CFO Assistant generates financial impact forecasts for various operational scenarios. This enables the selection of a path that is not only technically feasible but, above all, the most profitable in the long term.

Margin Protection Blueprint: The output is a concrete Cost-Benefit analysis and a financial risk checklist, ready for immediate implementation in your negotiation or operational strategy.

> Project Agent

The Architecture of Your Decisions.

This isn't a chatbot for summarizing literature. It's an operational module that transforms information chaos into a precise action plan. In critical situations - such as a failure of 15 transition elements (TPs) - the Project Agent becomes the foundation of engineering synchronization.

Key Engine Specifications:

Framework-Driven Reasoning: Assistant operates on the mapped logic of leading structural standards (including PMBOK, PRINCE2, Agile, Scrum). Decision-making processes are additionally filtered through the paradigms of global leadership literature, eliminating cognitive biases and theorizing.

Triple Solution Architecture: A unique algorithm that generates three paths to resolve any issue:

EASY [Quick Win]: An MVP-style solution that minimizes response time.
NORMAL [Standard Process]: A balanced process approach.
EXTREME [Radical Transformation]: Aggressive change with maximum impact on the project structure.

Implementation Blueprint: Each chosen path is immediately translated into a rigorous risk analysis and a ready-made checklist, eliminating the gap between strategy and action.

_____________________________________________________________________________________________________________________________________________________

The Chain: Operational Dossier

Strategy

Human Factor

Operations

03. The Chain

The complex challenges of offshore wind don't have one-dimensional solutions. That's why

SiteAI Chain doesn't look for simple solutions, but conducts a multi-vector analysis of the situation.

The system weaves the challenge through three critical pillars: hard financial mathematics, engineering precision, and leadership psychology. This ensures that the final decision is not only profitable but also operationally feasible.

____________________________________________________________________________________________________________________________________________________________________

Narrative and Stakeholder Management.

Translating difficult technical decisions into the language of customer benefits.

Creating a secure communication strategy that protects authority and business relationships.

Assistants:

> Mindset

> Development

> E-Mail

> Resilience Coach

Technical Feasibility and Error Elimination.

Root Cause Analysis (RCA) based on hard data.

Verification of whether the recovery plan (e.g., IRATA) complies with standards and is feasible for implementation within the current weather window.

Assistants:

> Kaizen

> Process Map

> Decision Tree

> Mind Map

Margin Protection and Liability Verification.

The system analyzes the contract for claims.

It simulates the impact of decisions on cash flow and the project's final outcome before you spend a single euro.

Assistants:

> Project Agent

> CFO Project Management

> Schedule & Decision

> OKR + 4DX

> Stakeholder

> Framework & Inversion

Live Demonstration

Crisis Response

Autonomous Workflow Execution.

03. THE RESULT (GENERATED REPORT)

The system generated a comprehensive Crisis Response Memo covering:

1. Crisis Context: Defined the clash between the crane failure, the 20-day weather window, and the "First Power" deadline.

2. Decision Analysis: Compared Option A (Wait for repair - High Weather Risk) vs. Option B (Charter - High Cost).

3. Recommendation: Immediate Charter (Option B). Rationale: The €3M cost is recoverable; missing the deadline destroys Investor Trust.

4. Risk & Stakeholders: Strategy to mitigate the Board's budget concerns and manage the Contractor's (MarineOps) defensive reaction.

5. Team Strategy: Specific protocols to manage crew burnout and safety (HSE) during the vessel switch.

6. Action Plan: A checklist of immediate next steps (Legal, Logistics, Communication).

ATTACHMENTS (VISUALS):

Decision Scenarios: Monte Carlo simulation showing a 40% failure probability for the Repair option.

Process Map: Implementation Workflow. A strict Sequence Diagram showing the order of execution for the next 48 hours (Approvals -> Mobilization -> Crew Briefing).

SYSTEM STATUS:

REPORT GENERATED. READY FOR EXPORT.

02. THE PROCESS (CHAIN EXECUTION)

01. THE INPUT (PROMPT DATA)

Command: "We received information from the subcontractor (MarineOps) that the installation vessel 'Poseidon' has suffered a main crane failure. Repairs will take 14 days. The weather window closes in 20 days.

We have 8 foundations on deck and another 12 at the load-out port. The Client is pushing to meet the 'First Power' deadline. The team is exhausted after the last sprint.

I need to make a decision: Wait for repairs (weather risk) or charter a replacement vessel (cost +3M EUR, but schedule certainty)."

Context Loaded:

📄 Project Scope (Tech specs & Timeline)

📄 Status Reports W42-44 (History of failures)

📄 Stakeholder Map (Client: Marcus, Contractor: Lars)

📓 Thought Journal (Pressure & Morale analysis)

Decision: Analyzed scenarios (Wait vs. Charter) vs. Weather Window & Budget.

Stakeholder Agent: Predicted reactions: Client (Time), Board (Margin), HSE (Safety).

Resilience Coach: Addressed team burnout and validated my intuition about the Contractor.

Project Agent: Synthesized data into the final Executive Recommendation.

Process Map: Visualized the vessel swap timeline.

Demo Transcript

Original: Polish // Translation: English

____________________________________________________________________________________________________________________________________________________________________

04. Strategic One Pager

Decision tree and communication strategy.

Cost comparison (IRATA vs Scaffolding).

Optimistic, Realistic, Pessimistic.

Hard evidence (Cold Impact Test).

Chain result. Battlefield Report Completed.

3 Scenarios

Analysis (RCA)

Implementation

Decision

____________________________________________________________________________________________________________________________________________________________________