Ask us a Question
Want to know what it's like to work at PageUp? Read conversations from our Insiders

How do you ensure that junior employees contribute their ideas?
Brad B. asked a question to Brad B..
- 1 replies
- 11 views
- Category: role description
- Date asked:
- Last update:
-
Brad B. Cto
Speaking from the perspective of how we do this in the Product Team, we follow an Agile process for estimating and planning. The Agile process naturally lends itself towards gathering wide feedback and actioning it, often referred to as âcontinuous improvementâ.
Team’s have regular ceremonies that are structured to enable (and almost require) everyone to have input into the discussion. These take the forms of sprint retro sessions and planning / estimation sessions where individuals are able to contribute their ideas, feedback and points of view in a non-confrontational manner.
Retro ceremonies leverage techniques that make it more comfortable for everyone to contribute such as using written sticky notes to contribute feedback as part of the discussion. People often find it easier to provide feedback in written form as opposed to having to speak up, and we find we get much better outcomes by leveraging this approach.
Planning sessions often require estimation and a key part of our estimation process is that everyone provides an estimate for each user story. This process naturally lends itself to promote team wide discussion on any estimation variances for each user story, allowing everyone to contribute to the final scope and design.
All team members will also have regular (weekly or fortnightly) 1 on 1 meetings with their people lead for coaching and development purposes. This gives team members the opportunity to relay or validate any ideas they have if they don’t feel comfortable doing this in a group setting, although we do find that team members in our culture are ok with contributing directly.
We also aim to keep our organisation structure very flat and non hierarchical. I personally ensure I’m having individual conversations with all team members at every level at least quarterly. I find these conversations give our team members the ability to raise issues or improvements they see as Product team wide. They also enable us to ensure individuals are getting their voices heard directly at the top most level, whilst also providing a lens into the wider product team, creating cross team opportunities for individuals.
Can't find a discussion that answers your question?
Recommended jobs for you
Senior Systems Engineer (6-month contract)
PageUp 423909 United States United States United States Technology Internal IT Fixed Term - Full Time, Full timeSenior Ruby Developer
PageUp 423903 Philippines Philippines Philippines Technology Development Full timeSupport Analyst (West Coast)
PageUp 423895 United States United States United States Customer Experience Product Support Full timeFind out more about our employees:
Dayne N.
VP Global Channels
Ethan N.
Software Developer
Keelan P.
Support Team Lead
Ken U.
Senior Technical Lead / Senior Principal Developer
Lauren M.
Senior Strategic Account Manager
Markus S.
Business Development Manager - Southern Region, Australia
Stacy S.
Technical & Support Manager - US
Will S.
Head of Client Success Europe