Danny · Tech Lead · Systems & Applications
Problems I solve
- We have 400 files in a spreadsheet: A case management system.
- Clients call to ask how their case is going: A client portal.
- We copy data by hand from one system to another: An integration.
- The site goes down when traffic spikes: Infrastructure that holds up.
- We all share the same password: Secure access.
- The form is endless and nobody finishes it: An obvious interface.
- Reports are put together by hand every month: Automatic dashboards.
- Using the system takes a training course: Design that needs no manual.
- Nobody knows what’s installed where: Documented infrastructure.
- We have the idea, but don’t know where to start: An end-to-end plan.
Keep it running
I design every system around how it could fail, so it doesn’t when it matters most. It makes for architecture that’s honest, with no shortcuts that come back later.
Your shift. The servers are about to start failing: tap them to fix them before they go down. You have 10 seconds.
- Time
- 10.0s
- Fixed
- 0
- Uptime
- 100.0%
Your best:
The translator
What I’m best at is the translation: understanding what a team actually needs when they don’t have the vocabulary to ask for it, and turning it into something they use without ever needing a manual.
✦ Quiz
The little chat window is a short quiz. Each question is a typical request, written the way any team would say it. Your mission: figure out what they actually need.
- 6 questions
- 3 options each
- Under a minute
How it works
- Read the request. It arrives like in real life: in everyday words, not technical ones.
- Pick what they need. Three options. If you miss, try another: only first-try answers count.
- See the solution. Every right answer shows, in one sentence, how I’d solve it.
“I want clients to know how their case is going without having to call us.”
What do they actually need?
What I do
I lead technology end to end. A process that lives in someone’s head goes through four states on its way to production.
- An idea in someone’s head
- A conversation
- A requirement
- A platform in production
What comes out of it
- Case management
- Client portals
- Integrations
- Infrastructure
- Security
Expertise
✦ Hover over or tap a panel to open it.
End-to-end delivery
From an idea in someone’s head to a platform in production, with one person accountable for getting it there.
Includes
- Discovery with your team
- Requirements in plain language
- Solution and screen design
Systems & infrastructure
The foundation nobody sees and everything depends on, designed knowing how it fails.
Includes
- Systems architecture
- Linux servers and cloud
- Integrations between systems
Internal platforms
Tools shaped around how your team works, not the other way around.
Includes
- Case management systems
- Client portals
- Operational tools and dashboards
UX & product
Complex processes turned into interfaces that feel obvious.
Includes
- Interviews and process observation
- Process maps and flows
- Clickable prototypes
What happens next
- You write to me. On WhatsApp or LinkedIn, in your own words: no tech knowledge needed.
- We talk. You tell me how it works today and what you’d like to change.
- I suggest a path. Where to start, in plain language and with concrete steps.