Concept party is an idea for growing yourself, your team and the whole R&D department through lectures power.

1. Concept PartyKnowledge Gathering

2. Using lectures to power
learning, knowledge
sharing, professionalism,
collaboration and brand

3. Team Concept Party
A random topic is selected for each team member from a pool of
concepts related to software engineering.
Each month the team meets for the concept party, and the team
member is responsible to teach the topic or part of it in 5-20 minutes
time frame.
There is a complete freedom on how the teaching is done:
presentation, workshop, or any creative idea.
The concept pool is open and everyone can contribute concepts.

4. Team Concept Party
At the end of all, there is a vote for the most valuable presentation
which will continue to the next level party.
The team should pick a facilitator of this meeting, to schedule,
randomize, and make sure team members are ready on time.
Participation is encouraged but not obliged. Consider a rule that
everyone in the room participating (if team is too big, split to 2+
sessions)

5. Team Concept Party
❖ The team constitute a psychological safe zone
❖ Small group of people
❖ Getting feedback from trusted peers
❖ Encourage discussions on how topic is related to the team day to
day work

6. 2-Team Concept Party
This party will take place relatively close to the team parties.
In this party 4 topics will be teached (5-20 minutes each):
- 2 selected topics, 1 from each team concept party (TCP)
- 2 new topics
- 1 additional presenter from each team will lecture about a
new (random) topic
A vote will be held for the most valuable presentation.

7. 2-Team Concept Party
❖ Gain confidence in presenting to other engineers
❖ Second iteration of winning topics (after 1st feedback)
❖ Sharing knowledge and language with another team
❖ Ground for sharing ideas and enhance relationships

8. R&D Concept Party
This party will take place once a quarter.
Each 2TCP winning topics will be presented.
A vote will be held for the most valuable presentation.

9. R&D Concept Party
❖ Bigger audience
❖ Third iteration for winning topics
❖ Stripping team jargon and knowledge assumptions
❖ Ability to teach topic for diverse set of skill audience

10. High level overview
Team Concept Party
2-Team
Concept Party
R&D Concept Party
2-Team
Concept Party
Team Concept Party
Team Concept Party
Team Concept Party
4-6 team members
4 topics
1 hour
1-2 in a quarter
8-12 members
4 topics
1 hour
1-2 in a quarter
~60 members
4-5 topics
1-2 hours
Once a quarter

11. Topic list
❖ The topic list is conceived by all of participants
❖ Process owner is making sure there are no duplications
❖ The topic list is live and changes regularly
❖ It's easy to add a topic to the list
❖ Topics are covering the widest possible areas in software
engineering, culture, work processes, and everything that is
related.
❖ Topics can be re-chosen for the same forum, but presentation
should take it to a new place
❖ If the same topic won in different teams, both engineers would
present it together

12. Why random topics?
❖ Fair distribution of learning
❖ Free people from paralyzing on topic decision
❖ Unpredictable benefits
❖ Out of the comfort zone

13. How should I build my lecture?
❖ Full freedom within the topic context
❖ It should take 5-20 minutes
❖ It can be the whole topic overview, or specific part of it
❖ Full freedom for type of teaching - presentation, workshop, etc.
❖ Should be built with audience skills awareness
❖ Team members should get time in the sprint for preparations

14. On what voting is based on?
❖ Presentation
❖ Clarity
❖ Innovation
❖ Inspiration
❖ Relevancy
❖ Importancy

15. Should I record my lecture?
❖ Preferably, yes.
❖ All topic presentations/recording should be available to anyone
❖ These materials should be approachable and searchable

16. Why lectures?
❖ When we explain something to other people, we come to
understand it better ourselves
❖ Teaching helps you develop the extremely important skill of
describing ideas well enough for others to use them
❖ The best test of whether or not you really understand a concept
is trying to teach it to someone else
❖ Your ideas will never be more effective than your ability to make
others comprehend them

17. Shouldn’t I be an expert before i’m
teaching others?
❖ No! Anything you can contribute will be helpful, and will set the
grounds for a discussion on the topic. think of it as sharing,
rather than teaching.
❖ The team should be a safe and empowering environment. After
couple of times you’ll gain confidence and could move to bigger
audiences.

18. What’s in it for me?
❖ Grow your knowledge
❖ Practice how you communicate tech concepts
❖ Opportunity for building an audience
➢ Recorded presentations
➢ Meetups
➢ Blogging

19. Meetup Concept Party
❖ Teaching complete strangers
❖ Stripping the company jargon and knowledge assumptions
❖ Professionalism
❖ Submit lectures to conferences

20. Meetup Concept Party
This party will take place once every 1-2 quarters.
The winning R&DCP topic will be presented to a broader audience.
The meetup will held 1-2 more topics, with related topics.
This event should be marketed properly to attract audience.

21. Meetup
High level overview
100+ members
Based on theme
2-3 Internal topics
External lectures
1-2 hours
Once every 6 months
~60 members
4-5 topics
1-2 hours
Once a quarter
R&D Concept Party
R&D Concept Party

22. High level overview
Team Concept Party
2-Team
Concept Party
R&D Concept Party
2-Team
Concept Party
Team Concept Party
Team Concept Party
Team Concept Party
Meetup
4-6 team members
4 topics
1 hour
1-2 in a quarter
8-12 members
4 topics
1 hour
1-2 in a quarter
~60 members
4-5 topics
1-2 hours
Once a quarter
100+ members
Based on theme
1-2 Internal topics
External lectures
1-2 hours
Once a quarter

23. Thank You!