How I, as a designer, work in a cross-functional setup with developers

How I, as a designer, work in a cross-functional setup with developers

Working with developers has been a core part of my journey as a designer over the past 3+ years. Whether it’s freelance projects or my current full-time role, I’ve gathered insights that I believe can help others navigate the complexities of cross-functional collaboration. Here’s what I’ve learned:

Differences Between Freelance and Full-Time Developers

Design Understanding:

  • Freelance developers often have a better grasp of design principles. They tend to translate designs into development with high accuracy.
  • Full-time developers, while initially slower to pick up design nuances, exhibit significant skill growth over time.


Creating Responsive Designs:

  • As a freelancer, I focused heavily on creating responsive designs that scale across different viewports.
  • This practice remains crucial in full-time roles but is often complemented by established design systems.


Progress Tracking:

  • In organizational settings, it’s easier to track development progress thanks to structured processes and tools.
  • Freelance collaborations allow for seamless design handoffs but can be tricky when it comes to monitoring progress in a systematic way.


Key Takeaways for Designers

  • Flexibility: Being adaptable is your greatest strength. Whether working with freelance or full-time developers, flexibility helps in overcoming challenges.
  • Communication: Clear and consistent communication ensures smoother collaborations, regardless of the setup.
  • Problem-Solving: Mistakes will happen. The ability to respond, adapt, and correct course is what sets a good designer apart.
  • Openness to Feedback: Always be open to feedback from developers and other team members. Constructive criticism can significantly improve your designs and processes.


Mistakes and Learnings So Far

  • Decision Making: Early on, I often made decisions based on what I thought was right without considering feasibility. This approach led to impractical designs and increased frustration for developers.
  • Documenting Communication: I didn’t always document communication thoroughly. This oversight resulted in misunderstandings and misaligned expectations.


Learning: I’ve learned to base my decisions on practical feasibility and to document all communications clearly. This ensures that both design and development are on the same page, leading to more successful project outcomes.

In conclusion, working in a cross-functional setup requires a blend of flexibility, communication, problem-solving skills, and openness to feedback. These experiences not only enhance your ability to work with different types of developers but also contribute significantly to your growth as a designer.


#Design #Collaboration #Development #Freelance #FullTime #Teamwork #Growth #Flexibility #Learning

To view or add a comment, sign in

Insights from the community

Others also viewed

Explore topics