userium

https://www.evcourse.com/ smart EV charging help

Accessible charging help (iOS app for scanning EV charger screens and car displays) https://www.evcourse.com/

I resurrected my web usability checklist from 2013, because I think we need it again. I first published the original checklist in 2013, now thirteen years later, the same principles still apply. You can copy paste all the prompts into your AI tool to audit any website.

Catch common usability problems before user testing.

Thank you! Good tip, I'll update the miles/km

I'm working on https://www.evcourse.com/ (I work in the EV industry)

I built this because clients kept asking "What's XXXX company planning?" and I'd spend hours digging through job boards and patents.

So I automated it. What companies would you like me to add?

Are you doing AI risk assessments?

True. Even if we don’t say a word, we still communicate non-verbally.

Also, cultural differences have a big impact on how we experience silence. For example, in Finland 'active silence' can be a sign of respect and showing interest by concentrating quietly, but some cultures might experience the silence differently than Finns.

Hi, creator here! TeamSuccess is a project risk management resource for agile teams. You can learn how to identify project risks, and increase risk awareness, with your Scrum / Kanban team.

How does your team manage risks?

Creator here, I'm happy to get feedback, or discuss!

We built a free Covid-19 Risk Assessment tool for workplaces https://finnovatec.com/

Here's one example audio version: https://teamsuccess.io/remoteteam

I like to write checklists and occasionally longer articles, for example;

* Usability Checklist https://teamsuccess.io/UX

* Remote Team Checklist https://teamsuccess.io/remoteteam

* COVID-19 Risk Assessment Guide for Your Project https://teamsuccess.io/risk

We wrote an introductory risk assessment guide, since we got lots of questions about the additional risks that COVID 19 introduces into projects.

"The government is also planning to close all restaurants and bars until 31 May."

Another free tool for setting weekly goals with your remote team: https://teamsuccess.io/

True, "Go to hackathons, get involved in open source", and build side projects. I just created a free goal board tool for remote teams [1], the best way to keep learning is by building.

[1] https://teamsuccess.io/boards/new

Hey! I created this, please let me know if you have any ideas or questions!

I find it interesting how they achieve this

There are lots of things, but one valuable thing is to build strong social connections [1] and trust [2] with your remote colleagues. For example by regularly getting the team together on video calls to discuss topics unrelated to work. And sharing a meal at the same time. Small things that make a surprisingly big difference.

[1] Guide to Remote Teams https://teamsuccess.io/remoteteam

[2] Harvard Business Review, The Neuroscience of Trust https://hbr.org/2017/01/the-neuroscience-of-trust

I know it's sometimes hard. I try to encourage my teams to give people the benefit of the doubt, rather than assuming something negative. It's a good way to combat defensiveness and important to building trust. In the end, it's a conscious choice to assume the best intent.

Exactly. Feature factories build features based on random assumptions, and not based on actual data.

I just wrote about this yesterday (https://teamsuccess.io/hdd). I work as a consultant with lots of Scrum teams, and many devs feel like they're just sitting in the factory, cranking out features. Without knowing whether they're adding real value to the end-user.

So what can you do to break free from the feature factory? Something that I recommend for the teams I work with, and noticed that actually works, is "Hypothesis-Driven Development".

In short, replace the items in your product backlog with experiments rather than user stories. Instead of starting with a user story or epic, start with a testable hypothesis. Then run small experiments that will prove or disprove that hypothesis.

My favorite question nowadays is "Wait, why are we building this feature again?" :)

I agree, and that's why I'm a huge fan of Hypothesis Driven Development, which enables the whole team to know whether they're adding real value to the end-user. Usually, it's embraced by, using the term you coined, “engineering-minded pm”s, who understand the importance of developer happiness and thinking in terms of problems.

I'd add the struggle / time it took to really deeply comprehend what 'build, measure, learn' means in practice. And realizing that there is a more scientific approach to building good products. For example by using Hypothesis-Driven Development [1]. We wasted lots of time (and money) at the beginning with our own stupid assumptions.

[1] Hypothesis-driven development (HDD) https://teamsuccess.io/hdd

In companies, the biggest problem is their "risk culture". Some of these aspects apply also to individuals and families.

In short, a company "Risk culture" is the sum of the company's "shared values, beliefs, knowledge, attitudes and understanding about risk, shared by a group of people with a common intended purpose..." (as described by the Institute of Risk Management).

Why don't people plan for potential disasters?

It's not a high enough priority for them. People might occasionally think about low likelihood, high impact events. But they rarely make a detailed plan for how to reduce the risk.

"Risk management" is not just for projects and organizations. If you're a parent you probably do risk assessments (https://teamsuccess.io/risk) every day, without realizing it. And ultimately, just like managers, you too as a parent, are ultimately responsible for managing risks. :)

Creator here, happy to discuss project risk management! :)

"Basically what you do is to put "fences" around dangerous areas as a manager and don't confront them unless it is "too much" - where too much depends on a situation."

In your example, putting a fence was apparently an efficient way to mitigate the risk. Just like in risk management, you need to establish your risk tolerance and know in advance what type of behavior you are willing to accept.

Once you have identified the risk, discover the root cause, and then you can choose whether to avoid, accept, transfer or mitigate the risk.

Some risk often remains, and often new risks come as a result of controlling the original risk (https://teamsuccess.io/risk). For example, firing a liked employee might lead to others leaving too.

Lots of companies and teams don't establish a risk tolerance / risk threshold, which leads to managing the situation poorly.

Here's the link again: https://teamsuccess.io/

As a side project, I worked on https://stayintech.com/ It was fun to explore the Google Maps and Places API.

And also I updated my usability checklist https://stayintech.com/UX

True. Also, Google has a great Places Search API. You can build so many more things with the Google maps libraries, unlike with other maps. For example just built https://stayintech.com/ with Google Maps API, after considering all the available options.