Eight months. Too long? That is often how long a new specialist needs to rotate through your functions, learn their quirks, and start shipping meaningful design work. It is not the architect’s fault. It is the organisation that never built a **system for knowledge to move**.
For a year and a half you can pay senior-rate invoices while getting a **translator**—someone who, instead of designing solutions, is still learning why marketing will not talk to IT and what sales cannot promise for technical reasons.
Two shortages at once — and no, one does not cancel the other
Market scarcity is real. In Poland alone estimates point to a gap of roughly 50,000 to nearly 150,000 ICT professionals. The market is no longer hunting “pairs of hands to write code”. It wants solution architects who speak both technology and the business. The biggest holes show up in cybersecurity (~41%), AI and machine learning (~33%), and IT programme management (~30%).
63% of leaders
say their people are not ready for technology-driven change.
The skills gap is also a **design choice**. Even if you land the missing expert, knowledge silos can block meaningful progress for the next two to three years.
Hiring another architect does not replace **designing the organisation** so insight actually circulates.
Field story: a company hired an AI senior at a record rate. For the first quarter nothing shipped to production. Why? Nobody could explain where CRM data came from and which legal constraints applied. The architect walked straight into a silo — and stayed stuck there for a year.
Knowledge clumps together when nobody invests in the plumbing
At universities, bootcamps, and training programmes everyone sits in their own lane. Frontend learns from frontend folks, analysts from analysts, HR from HR. Nobody is routinely paired with someone who thinks differently. The same happens in companies: teams do not understand each other’s constraints — from how margin is calculated with finance to how long integrations really take in IT.
When a project needs three departments in the room, the first three months often go to inventing a **shared language**, not to moving the work forward.
A signal from academia
At the University of Warmia and Mazury in Olsztyn we see a trend every HR leader should notice: people in their forties and fifties are coming back to study. They want skills in domains that “did not concern them” a few years ago. They sense those domains will decide whether they stay employable. It is a blunt reminder of how fragmented expertise has become for anyone who built a career in a single lane.
The end of the lone patch
Within a decade narrow specialist roles in their current form may not exist the way they do today. AI eats repetitive work; low-code tools trim the need for classic developers. The edge goes to people who can orchestrate intelligence without losing sight of humans — and their fears.
Younger entrants often arrive with deep but narrow domain knowledge and little patience for organisational chaos. That is not something you “fix with hiring alone” — it is a **culture** shift. At the same time, people over forty bring context and stamina for building competence. You need **both** in an interdisciplinary crew.
How to grow architects inside the team
Instead of chasing finished seniors at trophy salaries, design a path that turns the specialists you already have into the architects you actually need.
From developer: systems architect
Teach the business model, not only frameworks. Show how skipping a meaningful alt text is not “just WCAG” — it is leaving **serious purchasing power** on the table in markets where accessibility is non-negotiable.
From marketer: process architect
Find people already automating in n8n or Zapier. Pair them with a senior engineer so their hacks do not calcify into **duct-tape architecture**.
Instead of “study leave”: a real rotation
A week with sales listening to customers beats a month of abstract “communication training”. It routinely **slashes** onboarding from eighteen months to a handful of quarters.
True agility does not come from tooling alone
It comes when developers understand conversion and counsel understand data architecture. If a workshop’s only outcome is learning a new SaaS button, you burned the budget. The real prize is **trading context**.
Operational checklist
Concrete moves, in order
A question for leadership: are you designing systems where knowledge flows — or only stockpiling it in heads that will walk out the door?
Working groups
Start the knowledge exchange
In our workshops we deliberately mix participants from different departments. Knowledge moves because people from different worlds finally ask the questions they never knew whom to ask. You can also write to connect@atypical.pl.