This message was deleted.

Keen to hear of SPACE themed human measurements that have helped you drive/justify productivity improvements.

Looks interesting @clayton this is new and looks super interesting!

🦗 s

🤣

We've used the components of the SPACE framework as a basis for how we measure developer experience (As far as productivity is concerned). We did quite a bit of research, after which we tailored a survey (Or more multiple surveys) that we send out regularly to engineers at OfferZen. Super open to sharing it so that others can win and hopefully we can get some feedback on how we can improve it. We even did a POC with DX and found out that they use SPACE as the base for their feedback too. Some really interesting (But also actionable) insights from doing it in this way, which also lent itself to the more quantitative metrics we were capturing in tools like CodeClimate and DataDog. We could finally say, "Woah, there's a massive bottleneck in X, here are the hard numbers; and here's what devs are saying about it".

Nice miro board @Kyle Gani I really like it 👍 What survey cadence did you end up with? (frequency & quantity of questions. There's quite a lot of questions on the miro board :) Did getdx.com move beyond POC? If not why not? Which products did you look at? (e.g. DevEx 360 compared to your own custom servey)

@clayton we ran 2 experiments: One, where we sent the full survey out once per quarter and the other was our POC with DX (where we opted for a fortnightly cadence, of about 4-6 minutes worth of time investment, with only a subset of questions). In terms of participation, we were at 100% participation on day 2 of the DX survey. For the longer-form one we only got about 70% participation after a week. Feedback from devs was that they preferred the shorter more regular surveys. Pricing was the only deterrent with DX in that, we couldn't justify the spend for the size of our team. We also have an internal capacity for analysis (Seeing as we do our own state of developer nation reports). In the end, we chose to set up our own automation through Slack (with shorter cycles) and get support internally for analysis. It gave us the control we needed and allowed us to be cost-conscious.

Hi All, adding to this insightful thread what has been our experience at Vidyard so far and would like to hear your feedback: • We are experimenting with the SPACE framework. (By the way, @Kyle Gani your miro template is incredible, thanks for sharing.) For us, we used Laura Tacho's Notion Template and we recommend each product/platform team to come up with metrics they want to be accountable for. The hope is that there will be some similar metrics that we can aggregate and become engineering-level. • We have started sending bi-annual surveys based on some guidelines: Ref. 1 - Ref. 2 - Ref. 3 - Ref. 4 • We are currently evaluating the DX tool (will be running a POC soon). We hope that this tool will make the whole process effortless with some automation and be our single source of truth for both qualitative and quantitative data. Eventually, we might evaluate the addition of a tool that focuses on quantitative data (we already use Datadog).

nice thanks @Jeanne Uwatowenimana lots of great references.