nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Should we set bad habits for new users if it makes it easier to onboard them?

Ashlea Shaw

Hi all, I've been working in agile environments for a couple of decades now and in the process of researcher user I have been looking at different onboarding journey's. I noticed the Jira Beginners Guide to Agile and although not a beginner I thought this would be interesting.

Overall the guide is very good for folks new or curious about agile however there was one question that I wanted to gain more opinions on please....

The question asks if you notice that a work process is slow how do you address it? I opted for the wrong answer, as I would raise it with the team to get their input and depending on their responses propose and invite ideas to resolve it. However the course stated the "correct" answer was to draft ideas and share with your team leader.

Keeping in mind this course is for beginners, I am wondering if that approach is a good precedent to set. We talk about autonomy and transparent communication and this answer felt like a red flag to me.

I'd be very interested in hearing what the hive mind thinks on this one...

Comments

Morgan Watts_9u2pqd

I personally think there isn't too big of a difference between the two answers provided.

If you're asking for your team's input about process improvement, I believe coming with prepared ideas to start the conversation is best for facilitating a healthy discussion. This falls in line with the "draft ideas" portion of the answer.

For the "team leader" portion of the answer, depending on the setup, that could be approaching the conversation during a team sync to collect input all at one time. It also could be- going to team lead, team lead going "good points", then brings it up to the whole team.

Since it's a question there has to be a "right" answer. I think a valid counterpoint is that vetting an idea through the team lead first is most efficient because it can use less cumulative time than the whole team thinking about solutions.

As for your ponderance of "if that approach is a good precedent to set?" I think going to the team lead first is always a healthy answer, especially for a beginner. It's like a "go ask Mom." When in doubt, ask the most immediately senior person to you for some guidance.

Ashlea Shaw

Thanks Morgan, I'd be interested to know your thoughts on setting a precedent with users? You covered the example well, do you think we should give the "safest" direction to new users or do you think that could create problems further down the track?

Morgan Watts_9u2pqd

@Ashlea Shaw Hmm. Personally, I would give the safest direction to new users even if it's foreseen to cause problems further down the track. Measuring how serious of a problem is the key. If the "problem" we're creating is simply process re-training as in "hey go to this person first, please " then is that really an issue?

Let's say the "safest" directions will lead down the path of a larger amount of re-work than simple re-training then probably not the best idea.

Is this the correct answer? I'm not experienced enough to answer with certainty, but sometimes the safest answer is the simplest.

Ashlea Shaw

Thanks @Morgan Watts and I think you hit the nail on the head - it is depending on the impact, isn't it? I don't think there is a single right or wrong answer either. Thanks again for sharing your thoughts

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

agile

easy-agile

habits

mindset