recentpopularlog in

dirtystylus : teamwork   107

« earlier  
Actually, on Twitter: "Been working for a fully-distributed remote work company for about 15 years. I think one of the difficult things a lot of orgs are going to discover is that there's a big difference between "surviving WFH" and "being a remote-friend
Been working for a fully-distributed remote work company for about 15 years. I think one of the difficult things a lot of orgs are going to discover is that there's a big difference between "surviving WFH" and "being a remote-friendly company."
Individual workers are getting tons of advice right now, my only input is for people trying to wrangle teams:
1. Don't judge or micromanage what people are doing moment-to-moment. Let them accomplish their tasks however works for them.
2. Others have said this, but it's true: move as much explanatory communication as possible to shared docs with commenting/suggestion turned on, and a deadline for "closure."
3. Realtime meetings (esp with video) are cognitively and psychologically intensive, esp when team members are working in new/stressful/unfamiliar environments. Whenever possible save them for celebration, connection, ideation rather than information-dumps.
4. As a team lead/manager, dialing up the amount of time you spend in 1:1s seeing if people have what they need, and how they're doing, should be going up rather than down. When remote, you can't rely on "pass in the hall" nods and greetings to weigh how everyone's doing.
5. Finally, as a lead or manager, you have to be gentler on YOURSELF under current circumstances, too. Lots of things are going to fall through the cracks because there are more and bigger cracks. Tho it's not remote-specific,
has lots of great advice in "Managing Humans."
remotework  by:jeffeaton  1:1  coronavirus  teamwork  communication  management 
6 days ago by dirtystylus
Coronavirus remote workforce: Working from home doesn’t mean working constantly.
Ideally, managers have also established work goals that are based on output, not activities. The way you assess whether someone is being productive is by looking at what outcomes they’re achieving, not by monitoring how they’re spending each individual minute of the day. And when it comes to those work goals, priorities will naturally need to shift for now. Things that can be pushed back should be pushed back.

Moreover, employers will need to extend grace to employees who are working at home under difficult conditions. Many employees will be working with their kids around because schools have closed. With young kids at home, those parents may be significantly more limited in what work they can complete, which is why, of course, in normal times most employers don’t allow parents of young children to telework unless they arrange separate child care. But that’s not practical right now. There’s no ideal solution here; the reality is employees in that situation probably can’t get as much done as their colleagues who aren’t simultaneously juggling child care. In normal times that wouldn’t feel fair—and yet it’s the situation right now. We certainly shouldn’t just fire everyone with kids or cut their pay dramatically. Instead, we’re going to have to recognize those constraints and be more flexible.
remotework  mentalhealth  coronavirus  teamwork  management  leadership 
18 days ago by dirtystylus
Through a design system, darkly. — Ethan Marcotte
But as I’ve had more of these conversations with clients, I’ve realized that most organizations have taken a pattern-led approach to creating their design systems. And given the early emphasis on solving the consistency problem, that makes sense: after all, when your interfaces are in disarray, it makes sense to document your brand’s visual patterns and front-end code, and identify opportunities for reuse.

That said, I think it’s high time organizations start creating their design systems with a more process-led approach. Rather than starting with design patterns, we need to looking at the ways our teams currently work, and then identifying how a design system would function within that broader organizational context. Given that our industry’s only just started to understand the scale of the systems we’re designing, I think this might be our best hope for designing systems that support the way we want to work.
by:beep  designsystem  designpatterns  communication  workflow  teamwork  productdesign  language 
19 days ago by dirtystylus
The death of Agile? – O’Reilly
The one thing I don’t see, and the one thing that more than anything else captures the value in Agile, is the ongoing conversation between the customer (however that’s conceived) and the developer. This is important. Agile is not, and never was, about getting developers to write software faster. (Scrum might have been…) Agile is about getting developers in touch with the people who are the actual users and customers, regularly and repeatedly, so that the project doesn’t inevitably wander off course and produce something (in the words of Douglas Adams) “almost, but not quite, entirely unlike tea.”
agile  process  workflow  management  teamwork 
4 weeks ago by dirtystylus
Slack rules of life | Seth's Blog
Create a new channel for every project.

Invite the right people to join the channel to work on it.

Every project has a beginning, and it has an ending as well. Don’t start a channel if you’re not prepared to end it.

When a project isn’t helping you reach your longer-term goals, leave the channel.

Direct messages demand clarity and care. And teams do better when communication is shared.

Remember that your reputation moves with you, from channel to channel.

Emotions are real, but emojis can be a distraction.
slack  teamwork  communication  techculture 
9 weeks ago by dirtystylus
Erin White on Twitter: "Some quick phrases for your toolbox when folks say/do something that's not okay (and you feel safe to say something): "That's not okay." "We don't do that here." "Choose a better word." "Can you tell me what you meant when you said
Some quick phrases for your toolbox when folks say/do something that's not okay (and you feel safe to say something):

"That's not okay."
"We don't do that here."
"Choose a better word."
"Can you tell me what you meant when you said _____?"
teamwork  language  workculture  management  leadership  via:lisamariamartin  by:erinwhite 
november 2019 by dirtystylus
The most disruptive office distractions, ranked — Quartz at Work
In a survey commissioned by office-equipment maker Poly and conducted by research firm Future Workplace, 76% of respondents said a co-worker talking loudly on the phone created a moderate, high, or very high level of distraction for them while at work in their primary workspace, making it the most commonly cited disruption in the survey. Noise from a co-worker talking nearby was cited by 65% of respondents.
teamwork  office  openoffice  distraction 
may 2019 by dirtystylus
A thread written by @morganknutson
A massive F U to Google Plus
Also a study in designer entitlement
google  productdesign  twitterthread  teamwork  techculture  googleplus 
october 2018 by dirtystylus
Do leadership, don’t learn it. – Matthew Cook – Medium
Get people talking. Collaboration can’t truly happen if your team is silo-ed, and becoming the conduit for that collaboration is a key element of leading. The ability to understand who’s not talking, whether it’s necessary that they do talk, and then facilitating the conversation is invaluable.

Teach your teammates. Many people balk at this one: If I’m not the leader and don’t have the most experience, what business do I have teaching other teammates? Shouldn’t someone else do that? No! Teaching isn’t only about the transfer of information from one person who knows a lot to another person who doesn’t. It’s about research, communication skill, encapsulating and contextualizing information for others, and then effort — putting in the time to bring someone else along. In fact, teaching others is a proven way to become better, yourself.
teamwork  leadership  communication  agile  management  mentoring 
june 2018 by dirtystylus
heyyy it's 10:01am so i'm gonna need you to ᵍᵉᵗ ᵗʰᵉ ᶠᵘᶜᵏ ᵒᵘᵗ ᵒᶠ ᵐʸ ᶜᵒⁿᶠᵉʳᵉⁿᶜᵉ ʳᵒᵒᵐ
collaboration  teamwork  humor  cat  slackfodder  meetings 
may 2018 by dirtystylus
Jonathan Eyler-Werve (@EylerWerve) | Twitter
How we work:

* Include everyone. Listen.
* Strategy first, then tools.
* Fail early. Innovate. Repeat.
* Learn onto documents.
* Define success with metrics.
workflow  teamwork  manifesto  workculture 
september 2017 by dirtystylus
Where should designers sit? – Org Design for Design Orgs
There is a third way, for companies with enough office space. Designers can have two seats — a primary one with their cross-functional team, and a secondary one with their design team (or with the whole design org). That way they still spend most of their time with their cross-functional colleagues, but also get time for critique, fresh eyes, fresh thinking, mentorship, etc., from the rest of the design team.
design  management  workflow  collaboration  office  workculture  techculture  teamwork 
june 2017 by dirtystylus
Lemi Orhan Ergin on Twitter: "Let's clarify: * Jira is not Agile * Open Source is not Free * Using cloud is not DevOps * Rituals is not Scrum * Developed is not Done"
Let's clarify:
* Jira is not Agile
* Open Source is not Free
* Using cloud is not DevOps
* Rituals is not Scrum
* Developed is not Done
code  workflow  teamwork  opensource  agile 
may 2017 by dirtystylus
The Secret Suffering of the Middle Manager - The Atlantic
The researchers had a hunch about the woes of middle management because it occupies what they call a “contradictory-class location”: Middle managers have higher wages and more autonomy than the workers they manage, but they earn less than their superiors and don’t get to make big decisions. Middle managers often have to enforce strategic policies from the top—ones they didn’t develop—on subordinates who might object to those new policies. Basically, middle managers have the stressful task of absorbing the discontent of both sides.
management  stress  workculture  teamwork 
may 2017 by dirtystylus
How to Manager
A manager's job is to empower (service), not control (authority).

So much pathology on software teams comes from somebody confusing that.😣
management  techculture  service  teambuilding  teamwork  workflow  1:1  twitterthread  twitter 
february 2017 by dirtystylus
18F Handbook - How to say no
Here’s one I pulled together after becoming a supervisor: a quick guide to saying no to all-the-things:
communication  teamwork  via:nicoleslaw  18f 
december 2016 by dirtystylus
“Content & Display Patterns,” an article by Dan Mall
Ten projects of this type along, I feel like I’m getting the hang of what to look for and how to design this way. For those that are a bit newer though, one of the exercises I often turn to when I’m having trouble visualizing a content workflow is to think about how my boss, my client, or I would manage and maintain the content. I do that by designing a fake CMS for the piece I’m working on.
webdev  designpatterns  design  webdesign  via:danielmall  content  contentstrategy  styleguide  workflow  teamwork 
october 2016 by dirtystylus
Agency Innovators | Sparkbox | Web Design and Development
So how do we choose what technologies to adopt and when? I encourage the team at Sparkbox to ask a series of questions that focus on goals and key traits of the technology. There are countless considerations, and these are some of the consistent questions we ask ourselves—those that hit at the traits we want to bring to our technology decision making, especially when it involves our clients’ futures.
teamwork  workflow  learning  learningorg  via:sparkbox 
september 2016 by dirtystylus
« earlier      
per page:    204080120160

Copy this bookmark:

to read