Dami Ojetunji has been a product designer for five years and works on research-driven solutions that are based on study and put the user first.

The way she does things goes against the idea that every plan has to be perfect and fully thought out from the start. Instead, she encourages teams to see early work like sketches, prototypes, and even failed projects as important steps toward uncovering deeper insights, not as mistakes.

This perspective allows for rapid iteration while maintaining focus on real user needs rather than superficial aesthetics

According to Dami,

“The design process is not linear, as it’s a cycle of finding out, getting feedback, and making changes.”

The goal is not to be perfect. It is to learn. By seeing design as an ongoing conversation with users instead of a finished product, she helps product teams stay flexible and responsive. This ensures that solutions change based on facts, not assumptions, and lowers the chance of making mistakes that can cost a lot of money.

One of the main things that keeps people from embracing imperfection is fear. They don’t want to be judged, be late, or lose respect.

It’s common for teams to avoid sharing work until it looks ‘ready,’ which Dami has seen slow down development and disconnect designers from user realities.

Instead, she advocates for cultivating a culture where early drafts are shared openly and feedback is welcomed as a tool for refinement.

This approach is especially important in fast-moving startups and emerging markets where conditions change quickly and assumptions must be tested early and often.

Dami’s experience shows that imperfect prototypes can spark better conversations with users and stakeholders because they can reveal problems that polished mockups might hide. We learn important things that help us make real changes during these imperfect moments.

Additionally, embracing imperfection supports inclusive design practices. When teams understand that their first attempts might not be universally accessible or culturally sensitive, they may include more voices and points of view before making a final choice.

“Design that thinks it’s perfect from the start leaves people out.” Dami points out. “Being humble when you iterate encourages people to work together and leads to better outcomes for everyone.”

This means prioritizing tools and workflows that encourage experimentation and quick validation. Dami often uses low-fidelity wireframes and hand-drawn sketches early on, which reduce investment in any single idea and invite more input.

She also says that it’s important to try the designs with real people, even if the prototypes are rough. It saves time and money to get feedback early on.

Dami’s commitment to imperfection also extends to mentorship and community building. Designers who want to get ahead should share work in progress, ask questions, and see mistakes as chances to learn instead of failures.

Being in a safe place like this helps build strength and self-esteem, which are both essential for growth in the dynamic tech ecosystem.

Tabs, her platform, is based upon this idea and brings together a wide range of African digital products at different stages of growth.

The goal isn’t just to show off polished success stories; it’s also to keep track of a lot of different projects, even ones that aren’t quite finished yet. This transparency helps product teams appreciate that good design emerges over time, often through trial and error.

As AI and automation tools become more popular in design, Dami warns against letting technology reinforce perfectionism.

While AI can speed up work, it should not replace the iterative, human-centered process that embraces mistakes as insights.

She states, “Technology is a tool to help creativity, not a way to get things perfect.”

Dami Ojetunji’s perspective on imperfection is a good reflection that design is always changing because people are curious, open, and want to learn new things.

If product teams shift their focus from perfect results to real progress, they can make solutions that are not only useful and beautiful but also adaptable and inclusive. This mindset helps designers navigate uncertainty with confidence and build products that genuinely meet user needs.

More about Dami Ojetunji

Dami Ojetunji is a product designer with five years of experience leading user-centered design, scalable design systems, and product strategy. She has shaped product direction at early and growth-stage startups, including Y Combinator-backed companies. She is the founder of Tabs, a platform that curates African digital products to simplify market and design research for product teams. Her work bridges innovation and access by spotlighting high-quality solutions from the continent.  Beyond design, Dami is a mentor and advocate for design education. She supports aspiring designers, speaks at industry events, and fosters inclusive design communities. Her mission is to use intentional design to solve real-world problems and empower people in the digital economy. 

Whether contributing to open-source projects, coaching junior engineers, or working on scalable apps, he sees engineering as something more than just technical execution.

“The most useful thing I’ve learned in my career isn’t a specific language or framework, it’s the ability to think through a problem, document it clearly, and collaborate with others to solve it,” he adds with a firm tone.

He has years of experience in backend and full-stack programming, developing systems that promote efficiency, security, and maintainability. His knowledge of cloud-based architectures and upcoming technologies such as blockchain and massive language models has established him as a pioneer in his area.

Beyond the technical, he’s engaged in the next generation of engineers by mentoring them through organizations such as Persevere and RefCode.

“You can teach someone how to write a function in any language,” he says, “but what makes a great developer is understanding how that function fits into a system, how that system scales, and how to make decisions that don’t create technical debt six months down the line.”

Mentorship, according to David, involves more than merely examining someone’s pull request or offering assistance on a difficult problem.

It’s about helping individuals develop the mentality needed to create robust software. He points out that many early-career engineers focus on syntax and tools, which are crucial but not the whole picture.

“One of the most valuable things I try to teach is how to debug well,” adds David. “When you’re stuck, where do you begin? How do you approach an issue methodically? How can you ask the appropriate questions?”

These are not skills taught in a traditional coding bootcamp, yet they may frequently mean the difference between an average and a great developer.

David Aniebo’s dedication to mentorship complements his engagement in open-source development. He has witnessed directly how the collaborative nature of open-source projects increases learning and creativity.

While some developers are hesitant to contribute to public repositories, questioning if their work is “good enough,” he urges them to take the risk.

“Your first pull request doesn’t have to be perfect,” he said. “It just needs to exist. Once you put yourself out there, you understand that the entire process of getting criticism, improving your code, and thinking critically about architecture is what makes you a better engineer.”

Open source has a big impact on current software development. Much of today’s infrastructure cloud platforms, backend frameworks, and even AI models are based on open-source principles.

Aniebo believes that contributing is more than simply giving back; it is also about staying on top of industry trends.

He points out that the top engineers are more than simply technology consumers; they understand how it is designed, how to expand it, and how to enhance it.

That broader view is what makes today’s developer position more challenging than ever. The sector is continuously developing, and engineers are required to wear numerous hats, including problem solver, architect, and communicator.

“Software development isn’t just about writing code in isolation,” he argues. “It’s about making trade-offs, aligning technical decisions with business needs, and ensuring that what you build is both scalable and maintainable.”

He claims that many developers struggle with the transition from producing code to thinking critically about the bigger systems to which they contribute.

As the debate goes to the future, David admits that the sector is not without its obstacles. The need for skill is strong, as are the expectations.

Many firms demand engineers who can produce rapidly while maintaining quality an increasingly challenging balance to accomplish.

Junior developers are under pressure to keep up with new frameworks and trends, whilst experienced engineers struggle to manage technical debt and successfully lead teams. Despite the quick pace and tremendous demand, he is hopeful about the industry’s future.

For David Aniebo, the most fascinating aspect of software development isn’t the latest programming language or tool; it’s the people.

Seeing someone he’s taught obtain their first job, witnessing a young engineer build confidence in their problem-solving talents, or just cooperating with colleagues on a difficult project keeps him interested.

“At the end of the day, technology is built by people,” he insists. “And the better we get at sharing knowledge, the stronger our industry becomes.”