@mialoira In my experience, it's often about reporting structure. If design is a stand-alone business unit, it's easier to assert a pov about business outcomes. If it's reporting into a traditionally business focused discipline like pm, I find it's often harder to be included in the convo
@amythibodeau I'm somewhere in this zone. I do a lot of system design work, which includes services that cross products and information architecture. It ends up being closely tied with taxonomy and defining what things mean via content design. Bc of this, my team includes our content designers
Attended a work event for women leaders to share their insights today, and this nugget was one that really resonated with me, "Careers are long, try to keep yourself in a place where you believe in your purpose".
I just told my hairdresser that "during the pandemic" I was doing my own grey roots as if the pandemic is over as I sit in a chair with two masks on π€£ What headspace is this?
Bad product leadership: Here is something we want you to design.
Good product leadership: We believe there is a problem with X, so we want you to figure out how to address it.
Great product leadership: Help us understand what our customer's problems are & how to address them.
Reviewing portfolios today and a candidate linked directly into their Figma files with comments intact which gave me such great insight into how they collaborate with coworkers. This level of sharing obv not an option for most people, but it really did paint a fuller picture.
@stephaniesell_ Do product, design, and engineering sit at the same level? If not, dig deeper into what that means for politics within the company to see if design is relegated to execution.