Tag: career

  • Hybrid Working is the Future

    Working remotely has been becoming more important as an option for prospective employees when searching for their next venture. If I have kids that sometimes fall ill, will I be able to attend meetings virtually and still take care of my business from home? If my car breaks down on the way to work, can I make progress on my presentation from the repair shop?

    These kinds of questions are running through the minds of current and future employees, especially in the tech space. Granted, most jobs in the tech industry can be done remotely. Software engineering, design, QA, and even product management, can all be as successful as a distributed team as a colocated one.

    I have a feeling that more and more we will see companies not just allowing X number of work from home days a week or month, and more of all the team is remote on Wednesdays, or something similar.

    Right now, I have about a 45 minute commute from my house to my office. As I’ve gotten used to the drive, along with the fact that I listen to audiobooks or podcasts on the way, it has become less and less of a big deal. Of course, I’d like to have a shorter commute, but for right now it could definitely be worse. I’ve spoken to people who have commutes extending over an hour each way, which I find ridiculous.

    Kramer getting on the train

    Of course, there is a case for a bit of a commute, as for many people it’s the only time in the day where we are completely alone with our thoughts, listening to music, a book, the news, or appreciating a bit of silence. I enjoy listening to an audio book while driving, but would I rather have two hours of my day back if I didn’t have to commute? Absolutely.

    The reason for remote working is not just about time in our day lost by driving or taking the train. When it comes to hiring, you really can’t beat the fact that you can hire anyone in the world, rather than those just in your area code.

    As rent prices in the Bay Area have reached astronomical prices, as well as cities like New York, Seattle, and Chicago, it just makes the most logical sense to have employees than can live anywhere rather than forcing them to be in one of those places.

    Companies like ZapierGitlab, and InVision have shown that teams can be successful even though they don’t work next to each other.

    Another common theme I’ve noticed, especially among designers, is that when they need dedicated time to get some work done, they choose to work from home. With most companies opting for open offices, with all the pros and cons that they come with, it’s no surprise that to be the most productive, employees can have a difficult time concentrating at the office and need to work from home to be uninterrupted. Ambient noise, meetings, getting pulled here and there by coworkers, etc. are all things that have an effect on employee productivity, when dealing with work that requires uninterrupted “flow” state concentration to be the most effective.

    annoyance at the office

    It’s easy to walk into any newer office and think, “Wow, all this is such a waste of money.” The physical perks, furniture, office space, and many other things contribute to this opinion.

    While I enjoy going into an office, seeing my coworkers and spending face-time with them, there is no doubt that, from a productivity and financial standpoint, remote working trumps working in an office. If I were starting my own company tomorrow, while trying at first to find workers locally, I would keep my search open, and allow remote employees from anywhere in the world.

    There are, of course, things that become an issue when working remotely, such as communication, transparency, and collaboration. But all these things can be overcome with good organizational design, effective tools, and a good on-boarding process.

    I don’t want to say that it’s as black and white as good and bad, because, especially at this point in my career, I appreciate being in close proximity to my coworkers, learning from them in person, and feeling like I am a part of a physical group.

    It’s difficult to argue the fact that a long commute, sometimes unnecessary office perks, and all the extra costs that fall under the physical office space, are not the best use of funds in all situations. I feel that hybrid working is the future, and starting today, most companies can stand to allow remote working when the employees deem needed, without compromising any productivity.

    Something to think about: Do you have a long commute to work every day? Are you able to work remotely if possible? If not, see if your company is willing to implement a program to allow for more flexible working.

    This was originally published on Prototyper.

  • Being the Only UX Designer on an Agile Team

    I started my UX journey as a solo designer, and I found the dynamic of being on a team is totally different than being solo. When you’re solo, you don’t have to worry about collaboration or going to a ton of team meetings. You have enough other things to worry about on your own, though.

    Having recently worked on an enterprise software team with Development, QA, and Product team members, I learned a lot about working together, design advocacy, and compromise.

    I wanted to share some of the things that I’ve found to be important when working as a UX Designer in general, especially as the only one on a team.

    Communication

    comic on the phone

    I’m sure I don’t have to tell any of you that communication is one of the most important factors when it comes to working on a team. Regardless of position in your organization, everyone needs to be a good communicator.

    *Being on the same page as your team is possible simply by attending stand-ups and staying active on team chats or emails.*Stay updated on what the team is saying and working on even if you’re not meeting that day.

    Be clear about the goals and responsibilities of the team. Everyone should know what everyone else needs to do so if anything comes up, they know who to go to for questions or clarification.

    I also learned to voice my opinions and concerns when they arose because it’s always better to talk about things too early rather than too late.

    Collaboration

    people working together

    UX design is never done in a vacuum, so working with others is integral to the success of design, even if you’re the only designer on your team.

    Personally, I worked very closely with my product manager, because he had much more domain knowledge than me and could help educate me on the more complex parts of our product.

    When I had a question on technical capabilities, I would go to one of the developers. Luckily for me, they were always ready to explain something to me or go over an idea and the technical feasibility of that idea.

    Although I was the only one doing the design work, I would frequently check in with my team to make sure I was on the right path.

    Advocacy

    megaphone icon

    As UX designers, we can hope that our teammates all understand what UX is and what our contribution to the product should be. Not everyone is lucky in this regard, so as designers we have to do our best to advocate for ourselves and our value.

    *If the team is talking about a new feature or changing an existing one simply by suggesting solutions, part of our job is to redirect attention to the users, the research, and the business goals.*

    By aligning these things in our thought process, we can make better decisions from the get-go instead of backtracking later.

    The team dynamic will reflect how they approach problems and view the UX process. Some teams will see the value in things like research and user testing, others will see it as a waste of time. We have to adapt to our own environments and try to get on the same page as our team as best as we can.

    Active Listening

    active listening

    Along with the other items on this list, this one is like a superpower if used correctly.

    When you’re actively listening, you are fully concentrating on what is being said rather than just passively ‘hearing’ the message of the speaker. This comes in handy when your team is discussing things like the product roadmap, sprint goals, or when a team member is bringing an idea of their own to the table.

    If you’ve concentrated on their ideas fully, you can give better feedback and additionally, get more out of constructive criticism that is bound to arise.

    When you’re picking up on things like the speaker’s behavior, tone of voice, and reasoning for their statement, you’re already ahead of the game when it comes to listening comprehension.

    Wrapping Up

    Obviously I’ll never be done learning, nor do I want to be, but these are just a few of the main things I’ve taken away from my time working on a team building software.

    • Communication
    • Collaboration
    • Advocacy
    • Active Listening

    Something to think about: As the only designer on a team, what kinds of things have you learned so far on top of these topics?

    This was originally published on Prototyper.