How my third email reminder from HR motivated me to launch my startup

Congratulations Shihab, and all the best for future endeavours.

The reason behind your motivation to start off things looks super-motivational to every aspiring entrepreneurs. BTW it seems like you got pissed off by the HR executive. :P

One fun question, is that HR guy still surviving at your previous organization for provoking you to start your own? :D

When an idea comes from an experience like that you are solving the same problem for many people. And you have turned things from idea to reality as well.

Congrats on your startup.

I had a question - From my personal experience the difference between a normal feedback (someone asking you directly) vs an employee survey are framing and scope.

For example, questions asking feedback on "leadership". Most people, specially freshman, care about feedback on the guys they are reporting to - it can be a lead, manager, director etc.

But the surveys tend to gauge all levels - project leads, managers and then company executives. So they put in questions like -

do you feel you get timely feedback? do you feel people are held accountable? do you feel you understand company vision?

etc.

Everyone attributes these to different people in management but then the HR tells them otherwise. This causes a lot of people to be disillusioned by the surveys from the time they start the careers.

How do you tackle this issue in your product?

I am actually going to recommend this to my friends in HR right away. Very impressive user experience.

I have not played with the product beyond the onboarding demo but I have to say the sign up was very impressive too and much to learn there for my own work.

Having worked with surveys over the years the problem I find is that testing takes longer and longer. Sometimes you are filling in a form and sometimes you will have an optional page, e.g. in a custom job application form you may have a page on education that only the person with a degree has to fill in, this implies two testing paths through the form and therefore doubles the time to test. So testing time goes up by the cube of form complexity, or so it seems.

Years ago it would take a whole evening to make a C90 compilation cassette of songs for someone. Just the interface of the cassette deck, turntable and other cassettes would mean that it would take 5-6-7 hours to put it together, even if you knew all the songs and knew what you were doing.

Nowadays if I want to put together a playlist for 90 minutes of music I could do that and think what I was doing to get it done in ten minutes, not hours. I wouldn't be using cassettes or record players or even CDs. Just tick boxes in a UI.

So the key thing for me is that how-long-does-it-take question and much like how with compilation cassettes you still had to play it back to test it, with a survey you need to do some testing, ideally with that test time not going up 'by the cube' of form complexity.