companies in the client portfolio
Field work within a multi-client portfolio requiring adaptability, ownership and service continuity.
Back to portfolio
A builder’s mindset.
Combining big-picture thinking with practical execution.
I am naturally drawn to ideas that can become complete systems. Curious and cross-functional, I connect technology, user needs, operations and strategy to turn a complex or still-unclear situation into a concrete project. Optimism helps me see what could be improved; evidence, constraints and dissenting views help me test that intuition.
- Systems thinking
- Applied curiosity
- Pragmatic creativity
- Ownership
- Critical thinking
- Service mindset
whoami --personality01 — Big-picture thinking
I think in systems.
My first instinct is to step back and identify the components, dependencies, risks and long-term effects. I want to understand how each decision influences the rest of a project.
A solution is more than an interface or a codebase. It also involves users, architecture, deployment, security, maintenance, costs and room to evolve. I therefore tend to think in architectures rather than isolated tasks.
This broader view helps me connect technology, user experience, operations, strategy and viability instead of treating them as separate subjects.
Making a solution work is only the beginning: it also needs to be useful, coherent, resilient and viable.
- 01Need
- 02Users
- 03Architecture
- 04Security
- 05Deployment
- 06Maintenance
- 07Business model
- 08Ability to evolve
02 — Applied curiosity
Understand in order to build.
I am interested in systems and networks, software development, artificial intelligence, infrastructure, cybersecurity, hardware, user experience, entrepreneurship and organisational design. To me, that curiosity only becomes valuable when it can be applied in a real environment.
- What can this technology actually do?
- When is it relevant?
- What are its limits?
- How would it fit into an existing system?
- How can it become a practical solution?
I learn mainly by exploring, testing and building. I do not claim to be a specialist in every field I explore; my strength lies in learning, connecting disciplines and identifying the expertise a project needs.
03 — Moving into action
From intuition to a viable project.
I enjoy situations that are still unclear and require the right questions, structured information and a direction that becomes clearer step by step.
- 01
Frame
Clarify the need, the people concerned and the outcome that is actually expected.
- 02
Connect
Map functions, dependencies, constraints and available resources.
- 03
Test
Build, experiment, learn from errors and challenge the original assumptions.
- 04
Decide
Compare costs, risks and value, then decide which paths genuinely deserve time and resources.
- 05
Build
Deliver something useful today without closing off what the project could become tomorrow.
04 — Strengths and counterweights
Strengths kept in balance.
I prefer to describe my strengths together with their counterweights. That is how their energy remains useful without distorting a decision.
- 01
Optimism ↔ evidence
I first look for what could be transformed, then test that intuition against data, costs, regulation, feasibility and dissenting views.
- 02
Creativity ↔ feasibility
An original idea only matters if it addresses a real need. I therefore translate it into features, resources, timelines, costs and decisions.
- 03
Ownership ↔ alignment
I am comfortable working independently when the objective, constraints and responsibilities are clear, while keeping decisions, blockers and trade-offs visible.
- 04
Rigour ↔ pace
I look for concrete, verifiable answers while distinguishing what is essential now from what belongs in a later iteration.
- 05
Ambition ↔ simplicity
I am comfortable with ambitious goals and remain open to unconventional paths when they rest on solid reasoning. I think ahead to how a product may evolve without making its first version unnecessarily complex.
- 06
Persistence ↔ impact
I look for the underlying cause rather than an unexplained workaround, while making sure I do not keep chasing a problem simply because I have already invested time in it.
05 — Professional conduct
Direct, human and professional collaboration.
I favour communication that is simple, approachable and precise. People should be able to raise an error or a disagreement without making it personal. A technically correct solution is not automatically a good solution; it also needs to be understandable, usable and suited to the people who will actually work with it.
- 01Clear without being cold
- 02Candid without making disagreement personal
- 03Precise without unnecessary jargon
- 04Technology in service of real use
- 01
Incident
- Stabilise and prioritise
- Communicate what matters
- Restore, then document
- 02
Ambiguous project
- Ask the right questions
- Structure the information
- Shape a clear direction
- 03
User support
- Listen and add context
- Offer clear options
- Follow through to resolution
- 04
Migration and handover
- Prepare and secure
- Validate with users
- Document so the team can work independently
06 — Cross-functional profile
Connecting expertise without pretending to replace it.
I do not fit neatly into the traditional separation between technician, developer, designer and entrepreneur. I can move from infrastructure to interface design, onboarding, the business model or the way a product is presented to a client. This cross-functional perspective does not replace deep specialist expertise; it helps coordinate it and prevents one part of a project from being designed in isolation.
What I bring to a project
- 01
Structure in uncertainty
Start with an imprecise idea, identify the essential questions and build an understandable direction.
- 02
A connected, cross-domain view
Consider technology, users, operations, costs, risk and future evolution together.
- 03
The ability to learn and adapt
Recognise what I do not yet know and acquire the knowledge needed to move forward.
- 04
Genuine ownership
Deliver the agreed need with its purpose in mind and suggest improvements within the agreed scope.
- 05
Constructive challenge without complacency
Test ambitious ideas and revise an assumption when it no longer holds together.
07 — Clear-eyed reflection
What I keep in check.
These tendencies are part of how I operate. I do not try to hide them; I aim to keep what they contribute while grounding them in concrete criteria.
- Opening too many paths at once
- Set explicit priorities and decision criteria.
- Seeing potential before every constraint
- Quantify assumptions and seek feasibility, real demand and dissenting views.
- Allowing the scope to expand progressively
- Separate immediate essentials from improvements for a later iteration.
- Staying with a blocker for too long
- Return to impact, a time limit and the opportunity cost.
01
02
03
04
My goal is to retain the ambition, depth and creativity behind these tendencies while keeping them grounded through priorities and measurable steps.
08 — Concrete context
Context, not a personality score.
My professional experience and public commitments provide grounding for this stated way of working.
students in the represented community
President of the ESIEE-IT student union from 2021 to 2023.
ComputerConseils
Managed IT services for small businesses and diagnostic tools since October 2025.
stated languages
Native French, professional English and spoken Arabic.
This profile is based on the public CV, documented assignments and working principles stated by Logan. It is not a psychometric test, a score or a guarantee of results.
How I work, in one sentence
Understand the system as a whole, turn the idea into a concrete plan, then build a solution that is genuinely useful, coherent and able to evolve.
Bring me an idea, an incident or a transformation.
We can discuss the need, the constraints, the risks and the path towards a concrete outcome.