@kieran you think that your design is the best way we have come up with to acheive the safest way to distinguish between returnShard and forwardShard. From the designs that I have seen, as I have said, I personally agree with you.

You might have missed this. This is what @mix has said:

(1A - pick a pack home page) I'm not a fan, think there are clearer ways to lead people to the pathways. But also, that page is minimal to build, so go for it and we can A/ B test with it

Mix has a different opinion on how to acheive the clearest way. I am assuming mix is also designing for safety.

The fact is - none of us are UX designers and we don't know. We have opinions which will need to be tested with Peers. We have a potential opportunity from the 7-11 of Jan at underExposed to work with acutal humans who are experts in this area. It would be excellent if we have a couple of branch variations BEFORE WE DO A VERSION RELEASE so that we can actually get some feedback beyond opinions.

The fact is that given our working rhytms and differentials on who is on the shop floor and when synchronous design meetings are REALLY FUCKING EXPENSIVE - as in there was a single window of 60 mins in our entire week which we managed to find cross over for our sync weekly meeting call - and the only way we could make that work is by me having to feed my kid, given them a bath and get them ready for bed at the same time as the meeting. Parenting level super human effort. I got a badge. Woo.

But the point I am trying to make is - right now, without our funding level and with our various rhtyms - we're doing the best we can.

Human Collaboration and Feelings Layer

Kieran is feeling not listened to and frustrated. In part this is because mix is jumping in and coding and rolling stuff out. Kieran you might consider doing the same.

Mix is feeling frustrated and worried that we're not going to hit targets. It might be good to clear state what targets you're aiming to hit, when and why.

Peg and Kieran have expressed concern about rushing and releasing extra versions which are not well thought through which, given we are designing security software, is dangerous as reputation is everything and each new version release adds complextiy overhead of support. This is really important we should discuss what we are trying to acheive by jan - I don't think it needs to be publicly released but can be a branch we can point EF at. That would be enough for me to work with EF on and advocate for more funding.

I am feeling resigned in the fact I can see where each person is coming from AND there are some emaotional blocks which are causing friction - I think we need to find a way of clearing this emotional block to acheive a more harmonions feelings layer.

If we were all in the same office this would not be happening. We're juggling different timezones, 3 of us have children < 2 so juggling babylyfe, we're juggling up coming holidays and travel.

As I have tried to express elsewhere I think the actual thiing we are trying to acheive right now is now a new release but delivering software ahead of schedule so that we can use this as a pointer for our discussions with EF. They have expressed this was meant to be a honeymoon period and that they are open to discussing in Jan the 2nd payment AND further funding.