I been designing professionally 6 years now. I could come up with questions of things I wish I knew 1 month ago. But if I had to write things for my first day I would say:
- Always communicate with your developers (Just cause you can think it doesn't mean it can be built in the timeline you have)
- Learn to read between the lines. Majority of the time what you hear and what they actually need are two different things. (Goes with Eli Questions)
- Start saying No or just say "Phase 2." This will help you stop feature creep in your ideas.
- Always mention your concerns in meetings. It may sway the client or have it noted incase shit its the fan.
- Majority of your sites will never look like sites on Awwards. Mainly due to time, budget, and client resources.
- There will always be a ongoing struggle between user needs and the clients wants.
Those are all really great points.
Regarding "Always mention your concerns in meetings", you never felt scared to lose a job if you voice your opinions while being new in a company? I mean, all these stories, tips, hacks sound so utopian. Nowadays, jobs are unstable, superiors aren't always nice or professional, or competent.
Pick a place where your voice is welcome. I've been scared before, but I've never lost a job for having a strong opinion that was well-informed and kind.
I'm flexible on the one hand, and ready to defend on the other. My personal advice is to always advocate for balance.
Sometimes you can't pick. You just accept a job because you don't have anything else. Maybe I just don't have luck.
Its more about delivery. Just say "My only concerns are X due to Y." Sometimes, I use user persona's and past feedback. However, it doesn't always work. Sometimes you will have to redo months later it, and it will piss you off. However, I have done that to my dev teams. I will always admit my faults.
I understand there are sometimes insane amount politics. One bullet I took out before I posted and wish there were more articles about it. It's feel likes a game of poker sometimes. Some projects you will need stakeholder support to push it forward. Other times the clients will bulldoze you and need to have a "gray haired" individual come in to moderate. Or you have an arrogant egotistical CD or PM, which you are better off moving off the team or learn as much as you can a change companies.
Learning to embrace ambiguity and driving definition is a large part of "growing up" as a designer. The notions like "design as a mindset" and "honing your craft" ring true for even seasoned designers to revisit.
Glad you think so! I agree!
Eli has been instrumental in my growth as a designer and I can say these are all things he preaches nearly every day. He breathes this stuff. Share with a junior designer. They'll thank you for it.
Invest in a good chair / laptop stand. If you're working 10+ hours / day it makes a huge difference in your posture. Wish I had known this earlier in my career.
That cover image looks super nice. Really impressive to scroll down on it.
Thanks men, followed you!
Unpopular opinion – I love gigantic header images, and I'm being serious. It's pleasing the whole way through the scroll, and especially when it's an awesome photo like the one you put up.
Thanks, I think they set a good tone for sharing ideas and clearing one's mind. I personally appreciate them.
the best thing you can do is mistakes (and learn with them). So mind, and at the same time don't mind too much because it's a learning process.
Absolutely. 100% agree.
I wrote a letter to a junior designer– advice, and tips on how to succeed in design.