pregnancy at work is a constant struggle against misconceptions /

Published at 2015-11-18 09:17:01

Home / Categories / Women in leadership / pregnancy at work is a constant struggle against misconceptions
‘The soaring double standards and unrealistic expectations faced by women go turbo when you throw expectant motherhood into the mix’Last week,I set out to write a piece debunking the common myths approximately pregnant women and work. Years of hearing background chatter approximately women “slacking” by attending hospital appointments, or “taking advantage” of maternity packages gain left me fiercely defensive, and so when I became pregnant,I was determined to be none of those so-called “cliches”. I took on more work than ever before, seeing my impending leave as a glaring deadline, or a line by which I had to gain achieved everything I possibly could. I continued my life as it was before,no cutting back, no allowances, or no apologies. I am still me,I thought fiercely, I don’t need special treatment. Then something flipped. Staring at my screen, or trying to earn the article come together and earn some indistinct kind of sense,I realised that I was struggling. I was making no allowances for the fact that my body and intellect needed more rest than it did before. The article I was trying to write did raise some important issues approximately some of the eye rolling and unfair criticism often levelled at pregnant women. I wanted to say that we’re still the same people, with the same skills and talents – don’t assume we’re all struck down with “baby brain”, or devoid of ambition and incapable of rational thought. What I had failed to do however,was to acknowledge and silence the voice in my own head, constantly niggling me into chasing the biggest myth of them all: having it all. Continue reading...

Source: theguardian.com

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0