Show HN: Retroospect – How was your work week?
retroospect.com
retroospect.com
The descriptions aren't "right" with what I'm trying to put down even if I understand which direction I'm moving the slider.
I'm basically treating it as a numeric scale anyway.
I remember reading some article about it where I think there were two axis; love vs hate and weak vs strong emotions I believe and by moving over the face you would see the facial expression change and select it by clicking.
That could also be an interesting approach for this...
1. The sliders are just bad. Make it a clickable 1-10 list of faces or just about anything else, really.
2. The descriptions are too specifically emotional. I'm stressed but not nervous, I didn't enjoy the week but it certainly wasn't tedious. Not a big deal but kind of jarring since that's the only info the slider provides.
3. Allow me to share with a limited team (on hipchat :-) and chart my team's progress. I'm not tweeting this info to my clients or facebooking to my friends and family ...
The point isn't the specific number, it's the general placement. And even more, it's the trend over time/comparison to average.
Love the slider.
Additionally, speaking of work/life balance, it may make sense to have a question in there about having enough time to enjoy life or something along those lines. But maybe it overlaps enough with one or more of the other questions (i.e. stress).
Rate your week, 1-10. I dunno, what is 1 even like? Are you asking me to compare to the worst possible week? Yeah, my week sucked, but I'm not in work camp or anything.
This has been the most straightforward way of asking this kind of question I've seen.
http://allpsych.com/wp-content/uploads/2014/08/likertscales....
I think that made the biggest difference on getting people to contribute. It felt like the data was going to represent me. This is probably a small experiment, but if you’re thinking about this mini-site as a form of lead generation for WorkShape…then your main goals should be around getting people’s credentials and having it spread to their coworkers.
I would highly recommend figuring out how to give people accounts without passwords needed up front. It should feel almost like a mailing list at the end of the survey…
“Thanks! Let us know your email and we’ll check back in on you next week.”
Bonus points if you explain clearly why tracking this weekly is good for them. Then in your confirmation email, you can say you generated a password and you can follow their stats over time through this login link.
Your secondary goal should be explicit as well (if it’s what I think it is).
“Want to track how your entire team is feeling this week? Send them a link.”
Repeat on telling them why that’s a great idea. Right now, everything seems a little too subtle. Of course, I know you were probably just whipping this up to get it out the door.
Again, the copy is the best part of this site. If you change anything on the interface, be sure to leave that alone. Good luck taking this further!
We do quite like the labels too, but I do recognise, as pointed out by others, that their presence could create a form of bias. I believe that the choice of wording could divide the audience, with some people connecting with the sentiment of each and some people not.
The concept of the survey is a neat idea, and could be a good thing for us try out.
The suggestion of adding in a prompt for inviting team members is also good, if we decide to go down that route.
Thanks again!
http://i.imgur.com/Pxla7fl.png (you might notice we had a really bad day in April, but quickly recovered)
What are you, middle manager, going to do about it?!
Just kidding, but I've had bosses in the past who would notice something like that, and attempt to correct by sending an email out suggesting that folks answer the survey with more happiness.
Because of the possibility for abuse, chances are high that some/many of the inputs are pure bullshit anyway - people saying they're happy when they're downright miserable, out of fear of being scoped out if they log negative results.
Just another management PR stunt so they can gloat about how happy their employees are, when the results may be fabricated. Perhaps this would work in a small company where downward trends in happiness result in immediate changes based on employee suggestions. For every medium and large sized company I've worked for, this would just be another manipulative game pushed onto employees by management who will never implement any real change but can show the CEO ridiculous charts about how "happy" the employees are.
tldr; Management loves to show off reports like these, but the values input are often meaningless and only serve to antagonize employees rather than help.
* An agile team could use this as part of their retrospectives, and could track the data points across multiple sprints to see trends, as well as "scoring" the latest sprint.
* Sometimes an individual in a team can be quite quiet and reserved, and won't physically speak up if something's not going so well. Moving to a system like this may give them a voice.
* The levels can be tracked both by the team and by an individual's line manager to keep an eye on those people who are consistently (or increasingly) bored, frustrated, not learning, or generally unhappy.
* If this were completed every day, then it would effectively become a Niko-niko calendar[1] (although you might want to fill out just a single data point if you're doing it every day).
* Having a daily version would also work as an early-warning indicator of trouble brewing within a team or project.
[1] http://agiletrail.com/2011/09/12/how-to-track-the-teams-mood...
In particular the point around quiet/reserved members of the team - this is certainly a medium that these people could be more comfortable with.
Also, great idea with the "Keep track" button at the end. Registration (and therefore conversion) becomes a part solving the user's problem ("How do I keep track of my work satisfaction?"). If it weren't for the slider, I'd definitely click it.
Having said that, I'd prefer a keyboard-only way to do it too.
Interesting. in the mobile first world.
Microsoft Surface devices are mobile.
iPads with bluetooth keyboards are mobile.
Developers also tend to spend quite a lot of time sitting at desktop-class machines with nice big monitors, because amazingly enough Emacs/IntelliJ/Visual Studio/whatever doesn't run on an iPad mini.
Eh. Why not? It's 2015.
Only reasonable explanation, right?
P.S We'll look into it.
Thanks for the feedback/suggestions.
Bit of background:
The concept is indeed inspired from our collective experience of doing retrospectives in agile work environments. We think the process is very useful from both an individual and team perspective and we want to encourage more of it. A lot of the time though, the data collected at retrospectives is lost (written on sticky notes etc) and not stored for later use. From an individual, and possibly team, perspective this is something we are interesting in addressing.
I can't speak for anyone else but weeks just go by and I rarely remember back to some of the positives and negatives I had from 2+ sprints ago, nor do I remember if all of them were effectively addressed.
Retroospect, in its current iteration, is an attempt to give some way to record your personal feelings towards things that usually feed into the retrospective process.
For more constructive feedback, I would take another look at some of the descriptions. For example, I felt like I learned nothing this week, but having the lower values of that question be "I haven't learned a thing since the 90s" greatly escapes the bounds of the week. I get that it's exaggeration, but for what it's worth I adjusted my score so it was above that description even though it should probably be lower.
I haven't checked out every value available, but it's worth putting some metrics on each option and seeing if sub-ranges in one category are used far less often than equivalent ranges in other categories. It's funny how descriptions can muddle a statistic.
Pull up developer tools, turns out there is actually a POST going on behind the scenes, which is getting a 503. So, there's probably overloaded servers, but it should would be nice if that were exposed anywhere besides the developer console...
Issue should now be resolved.
The issue was to do with the averages endpoint re-calculating every time it was called, this ate up alot the resources on the dyno - we've cached this now so this no longer happens.
It is still running on the same resources, no 'throwing' more anything at it at this point.
I would like a free form text field, a more like, "What's bothering you this week?". Some things can't be expected / measured by sliders, but may be important to a person to note historically.
In the hands of individuals it's a good tracking tool: I wasn't really aware that I was... maybe not as happy at work as I would have liked until I took this week's survey. I'm interested in the historic data too, after I put a couple of data points in there.
In the hands of Management, let's just say I'm very wary. Management can use this data to improve a bad situation, ("You're unhappy because we schedule meetings every day at 3 and you can't get work done? Ok, let's stop doing that"). OR more likely, especially as companies grow bigger, can just make the situation worse: ("Let's have an awkward conversation about feelings and why you're not hyper happy this week / I'll blow smoke up your rear so you'll feel better, but those meetings at 3? Yeah, not ever going to change")
Personally, I was neutral across the board. Instantly had me thinking "should I be poking around for a new gig?", even if responsibilities/life make that somewhat unpractical.
It's clearly a 1st prototype, so I'll cut a lot of slack on the mechanics. Overall it could be a great way for medium and large companies (where it's impossible for everyone to talk to everyone every day) to understand the sentiment of their people.
Keep going with this, please!
However, I've tried to do this kind of thing in the past, with a spreadsheet on my phone. Just ended up forgetting/deciding not to do it, even with a calendar reminder.
Will be interesting to see if the graphs and email reminders are enough to push me over the hump this time and give enough data to make it useful.
I'd love to see how my entire team feels on a week over week chart. It should be anonymous to the employer, but it'd be cool to see the stats. But I'm a chart nerd.
Being able to appear anonymous when sharing your data with team-member is somewhat debatable, I can see benefits on either side here. Ultimately I think if we do introduce this feature, and I strongly suspect we will, anonymity should be controlled by the user e.g. they can opt to share their name with team members or not.
If anonymity is optional there will also likely be some implicit pressure coming from management not to be anonymous, leading to people censoring their true feelings for fear of repercussions ("so, I've noticed for the past few weeks you haven't been happy or productive, maybe this is not a good fit for us")
Not sure, maybe I am being too negative, but when it comes to anonymity and workplace surveys my default setting is "the more the better"
Should it be opt-out of anonymity or opt-in?
Thanks
Its been shown in study after study, that people's response to surveys is extremely prone to suggestibility and situation. I remember a racial stereotyping survey with a movie afterward, where people who were told the movie was cancelled recorded as far less tolerant.
I like OP's idea a lot, however it will suffer from memory and social conditioning bias. This is why in Chronicle[1] I record these data points at the very moment they happen, and use the notion of "fold" to summarize them at daily/weekly/monthly level.
Would be great if it was possible to auth via Google, Facebook
Not directed at you specifically, but people waste more time complaining about signin options than actually going through the process. It's kind of funny.
If I rate what I learned this week at 0/5, it's labelled "I've not learned a thing since the early 90s". Cute, but not really the same thing.
Likewise, all the stress descriptions seem to be about workload.
[1]: http://www.se-radio.net/2008/07/episode-105-retrospectives-w...
[2]: https://www.adr.org/aaa/faces/services/disputeresolutionserv...
With these mood tracking apps however the outcomes are probably simple aren't they? If you're not happy at work whatcha gonna do? Get a new job or have an argument with your boss.
See here for an example: https://play.google.com/store/apps/details?id=com.ubhave.emo...
It's surprisingly intuitive, at least for the axes the devs of that app have chosen.
You should also look at building some sort of integration with Slack, so that I can look at and gauge my team's moods and progress during the week.
The quantified life crowd is still around, and being able to track different values over time is incredibly useful. Sure, you can use a spreadsheet or whatever, but a nice pretty site like this makes it really easy and fun.
Also, one thing you could do that might be interesting: add the ability to set up or manage teams. That way it can be used for team retrospectives, just as Slack is now used for standups.
Perhaps tie it into Github (using organisations and/or repos as the basic units of projects, similar to how waffle.io does to give an agile view of projects.
Interesting idea though.
Thanks for your feedback and ideas. We're certainly keen to add more features to the tool, qualitative feedback is definitely something put on the todo list.
How would you go about recording this? Freetext? Some kind of structured list of postive and nagative points?
That said, it depends on how you intend for this to be used: is it just for personal monitoring, in which case you probably want it as simple and seamless as possible (and free text notes might be just the thing).
If it is for teams, eventually you probably want more structure.
With regards to recording positives/neutrals/negatives - I like this thinking. This could be something that the user could record at any point in time during the week, knowing that it is safely stored (and remembered) for their next upcoming retrospective. I always remember getting ready for retrospectives and retrospectively struggling to recall what really annoyed and pleased me. To try and counter this we put a 'box of emotions' in the middle of each workspace where anyone could put a sticky note when they felt something that they wanted to record for retrospective!
I think the question about stress could use some tweaks, to the wording. What do I say if there was stress and I handled it well. But I dont want more. Im not going to say "I could have more" and im not going to say "I got nervous". I could however say stress was med-high.
The bigger picture for us, with Workshape.io and Retroospect, is really about understanding how happiness and work sit together and helping individuals, groups, and companies get access to this information in a format that can be used to make better decisions.
Whilst Workshape, right now, is a recruiting platform for companies who need to hire developers, we think its application is much bigger. We are looking into how to go about next steps to move into other areas and make it useful even if you aren't currently seeking a new challenge. Hopefully this would make Workshape and Retroospect very complimentary.
(Wish I could find the story about how it's better to have a few people who really love your product than a bunch who simply like it.)
I have some experience in happinesstracking as we do that for years in our company and I provide a similar web service for others. Some takeaways are:
- almost nobody wants to track every day
- many people want to track by events (something very good or very bad happened)
- it's more valuable, if you track a complete team or company and share the insight
- just ask for one metric, make all others optional
All the best for you guys, I love all the other people & services that do mood/happiness/satisfaction tracking/metrics.
I definitely agree with all your takeaways!
EDIT: now they've sent me 8 welcome emails. Hmm
It is heavily inspired by the process of agile retrospectives [1].
Hope that helps clarify.
[1] http://searchsoftwarequality.techtarget.com/definition/Agile...
I do also wonder, if someone who feels unhappy in their job is more likely to sign up to our service, that someone who is not. This could be a side effect of the product being something that is currently just aimed at individuals for their own personal use.