Sign In

Oliver Taylor

Highlights

Feb 19 · linkedin

Don't be fooled when a developer simply says 'yes’. "Yes, I can" - without context 🚩

It’s so tempting and easy for developers to give simple and ‘easy’ answers. The issue is that most of the time when you speak with developers you’re having what I like to call “iceberg conversations”.

So much complexity and context is hidden within iceberg questions. They attempt to rollup the details needed to understand the situation into bitesized chunks. This might sound like a great thing. What’s not to like? The developer is simplifying something you hired them to do and giving you a simple straight answer.

Problem is, uncertainty exists in EVERY project. To truly collaborate, developers need to highlight the project's risks. This avoids surprises and keeps everyone on the same page.

We can avoid uncertainty, misalignment, and unexpected delays by staying on the same page. A good project prepares all stakeholders for where surprises may arise and optimizes for consistent alignment across disciplines.

Avoiding this requires effort from both sides of the skillset: 🤝

1 - We should all foster relationships that are open to learning and invest in the time (or processes) needed to align all stakeholders.

2 - Non-technical stakeholders should be comfortable asking questions, and open to learning just enough to understand technical constraints the project is currently facing.

3 - Technical stakeholders should be aware of where unknowns lie in a project, and be prepared to communicate these concepts well enough that all stakeholders have language needed to contribute to the conversation.

The best kind of developer communication isn't about always saying "yes". It's about fostering clear understanding of risks and potential challenges.

...because let's be honest, "surprise roadmap changes" never make anyone happy.

Feb 12 · linkedin

Can you keep up with developer talking shop? This is what we’re doing to keep the conversation inclusive:

I really enjoy the challenge of taking complicated web ideas and making them understandable for everyone, whether they're tech-savvy or not. This skill is crucial, not just as a personal achievement, but because it underpins a core belief of mine: inclusivity in web projects is indispensable.

Inclusivity means ensuring that everyone—regardless of their technical background—has the opportunity to contribute to and engage with a project. It's about dismantling barriers and creating spaces where diverse perspectives lead to richer, more innovative outcomes.

Here are some of the things I do to prevent these barriers:

👉 Avoid or explain acronyms when the full name describes what we’re talking about.

👉 Provide mental models for thinking about how systems work together Use metaphors when the nuance of the topic isn’t essential

I’ve been updating a living article with some terms I often need to explain or break down. Can you think of anything else I should add to it?

Related Questions

What is the person's full name?
What is their first name?
What is their last name?
Is a profession or role provided in the details?
Oliver Taylor
Add to my network