Unpacking the truths of Human-centered Design, organizational culture, and senior practice.
Since 2014, I've delivered high-impact B2B/2C SaaS solutions for industry leaders like IBM, Broadcom, Foxconn, and GoTo. My approach combines a technical foundation, rooted in my early contributions to Ubuntu GNOME, now just Ubuntu, with a rigorous commitment to user-centric problem solving.
Human-Centered Design (HcD) is often misunderstood as a phase or a set of artifacts. In reality, it is a risk-mitigation strategy. It requires a culture that values rigorous experimentation over the 'HiPPO' (Highest Paid Person's Opinion). While the industry often treats UX as a linear progression of Jira tickets, true product discovery is non-linearβit's a continuous cycle of unearthing technical constraints and user friction before a single pixel is moved.
I approach topics in a systematic way, ensuring a holistic perspective whilst selecting the most suitable approach for each distinct problem. Just as you wouldn't apply a consumer-facing gamification tactic to resolve a mission-critical data bottleneck in a mainframe, UX practitioners must select tools based on the scale of the system and the gravity of the userβs task. This process is inherently non-linear; it requires ongoing collaboration and the ability to adapt based on user feedback to drive continuous innovation.
That said, I seek an environment that embodies:
User-Centricity as Practice: Where design decisions are reliably driven by ongoing, non-negotiable user research, not internal politics or HiPPO.
Ethical Product Mandate: An environment that actively rejects deceptive patterns, dark UX, and the short-term optimization of metrics at the expense of user trust, privacy, and long-term well-being.
Systemic Clarity & Empowerment: A culture that structures its product and engineering teams to reduce organizational silos and bureaucracy, enabling designers to focus on complexity reduction and creating clear, accessible, and high-performing solutions.
I wrote this piece to highlight the factual divide between User Experience Design and any form of Visual Design. If that reality doesn't match your project goals, you probably do not need a UX designer.
The traditional UX hiring pipeline is fundamentally broken, relying on the shallow benchmark of portfolios and performance theater rather than a true understanding of the craft. While portfolios are effective for showcasing visual design, they fail to measure actual expertise due to the attribution problem, where team achievements are presented as solo work, and the NDA barrier, which forces candidates to hide their most impactful projects.Β
Furthermore, forcing senior-level practitioners to endure whiteboarding or takeaway exercises is a major π© that signals a fundamental lack of trust. These arbitrary hurdles indicate a culture where the UX role is undervalued and mispositioned, whereas true product design chops are best uncovered in an interview setting by asking the right questions.Β
This systemic failure stems from a misunderstanding of the discipline itself, as design thinking is not a solo performance but an ecosystem relying on discovery, cross-functional alignment, and genuine user engagement. For example, a senior designer shouldn't be judged on how beautifully they draw wireframes alone on a whiteboard, but rather on how they facilitate collaboration between engineering, product management, and real users to solve a complex problem. Organizations that treat UX as an isolated, transactional output fail to recognize this distinction, and they will inevitably alienate the very talent they need to drive innovation.
Performance is often measured by proximity rather than impact because of the misconception that physical visibility equals productivity. Just as a "wow factor" doesn't guarantee a usable product, a occupied desk doesn't guarantee a solved problem. Why this fails high-impact design:
Deep work vs. distraction: Deep work requires long blocks of uninterrupted focus. Micromanagement and forced visibility prioritize the feeling of control over the reality of results.
Trust as infrastructure: High-trust, distributed environments enable practitioners to focus on complexity reduction and system-wide clarity. When a culture prioritizes "being seen," it inevitably creates a bottleneck of bureaucracy and performative activity.
Optics over output: I prioritize environments that measure success by the quality of the solution and the health of the system, not the hours spent in a chair.
True professional expertise requires the autonomy to work where and how the problem is best solved, which is why if an organization relies on visibility to verify value, it indicates a fundamental lack of maturity.
Research, Brainstorming, Automation. Beyond the routine, AI serves as a powerful catalyst for human potential, functioning as an advanced collaborator.
Rapid synthesis: Combing through vast datasets to instantly extract key insights and trends.
Information retrieval: Sifting through global literature to surface relevant papers and case studies in seconds.
Knowledge structuring: Organizing complex, fragmented data into clear, actionable foundations for deeper study.
Idea generation: Sparking unexpected concepts and creative angles to break through mental blocks.
Perspective shifting: Simulating diverse viewpoints and scenarios to pressure-test ideas.
Collaborative iteration: Functioning as a tireless sounding board to refine and expand raw thoughts.
Workflow optimization: Handling repetitive, time-consuming tasks to streamline daily operations.
Time liberation: Reclaiming valuable hours so the focus can shift to high-level strategy.
Ultimately, AI is a tool, not a substitute. While technology can process data at incredible speeds, it cannot mimic the empathy, intuition, and human feeling that define true connection. AI can assist with the work, but the heart behind it remains entirely human.
I do not share personal identifiers, including my full name, phone number or location, until a formal offer or compliance-mandated background check is underway. Iβd like to briefly clarify the reasoning behind this, as it reflects my professional diligence:
Asynchronous equity & documentation (The Paper Trail). Written communication via email ensures a clear, timestamped record of all discussions. This protects both parties as it eliminates the "he said, she said" around salary negotiations, role expectations, and verbal offers. Furthermore, it removes unconscious bias related to age, accent, or background, allowing my qualifications and written articulation to be the primary focus of my initial evaluation.
Account security & cyber hygiene. As you likely know, a mobile number is the primary recovery key for nearly all digital platforms (email, banking, cloud infrastructure). Sharing this asset broadly across multiple ATS platforms and recruiter inboxes exponentially increases my exposure to SIM-swapping, SMS-based 2FA interception, and vishing attacks, threats that are increasingly prevalent in the remote-work landscape.
Data permanence & breach mitigation. Resume databases are prime targets for data brokers and malicious actors. Unlike a password, a phone number cannot be easily rotated or changed without disrupting one's entire personal and professional network. By limiting its exposure, I drastically reduce my long-term vulnerability to doxxing, OSINT profiling, and the permanent surge of spam that follows a data scrape.