Thoughts: Pair Testing…sort of

Pair Testing

At the beginning of the year, I attended TestBash in Brighton and there was a talk that just stuck with me with practical application.

This was the talk by Katrina Clokie on Pair Testing. She even outlined how she trailed it in her job.

I recently got a buddy at work and we were talking about sharing knowledge. I really wanted to try pair testing, so we did a version of it.

Step 1 – finding the right task

The team did some work on a tool that I wasn’t too familiar with and as part of our development process we created a testing mind map.

During coding the developer will use this mind map to test his code and depending on risk and sadly often time, the tester will also do some testing using the mind map.

In my pair testing example, the developer had done some testing and so had I, noting down some questions before involving my buddy. I then walked him through what we had tested so far and how the application was working.

Step 2 – What happened

Just due to different experience and knowledge he asked some other valuable questions which aided my testing to go a bit deeper and got us thinking of other testing types such as performance and database behaviour.

For me this was an invaluable experience, as I learned to think about other testing types and techniques and scenarios and I think for my buddy it was also a great experience as he got to see bits of the company’s product catalogue he wouldn’t necessarily get to see on a day to day basis.

I want to try and make this a more regular thing, and also try it before I test something and let the other tester drive.

The other side of this is, that we have a weekly test team meeting and I will try to show features or functionality that the other members may not necessarily see but may have to pick up, when I go on holiday. During this session we can also ask valuable questions of the new feature or product. Which is easier than listening to a monologue when handing something over. I think!

As testers I feel we generally want to know about the company’s products and about all the things they can do for customers and ourselves, so that is also why I envision this knowledge share to be good.

Do you do regular pair testing sessions? How do you structure them? Do you do knowledge sharing sessions with other team members?


Thoughts: Encouraging change when you are the only tester

Sometimes things come from small conversation snippets.

Some of you may know that I did a testinginthepub episode not too long ago. In there I talk a lot about what is awesome in my job now, like being valued as a team member, being invited to kick off meetings (these help us talk about what we are building and why)  teams ask me for mind mapping the testing areas.

However this was not always the case. It is important to remember that anyone can encourage change. I was not here before the changes so I will base my advice on what I did in my previous role as the first and only tester.

I did a talk on this last year at Tiny Testbash as well. The recording is available through the dojo subscription.


Encouraging change when you are the only tester.

In my previous job, I was introduced into a company which had a successful product that was starting to make them money but they had no testing department. When I questioned how they test their product I got the following answers:

“We don’t have any testers. Our product owners and stakeholders do the manual testing and we have a vast suite of front end automation tests.”

Nevertheless they decided to hire me, and subsequently a team of tester. How this came about and some learning along the way is what I would like to share below.


The problem:

So I mentioned that the company had a successful product, they had people testing it and a vast suite of automation tests. So what was the problem? The company was 6 years old at this point, had moved to their version of agile software development and the need for a fast feedback loop from the product owners and stakeholders was becoming apparent.

However these individuals generally already had a full time job and could not attend stand-ups, reviews, planning meetings, let alone test the product. More often than not the stakeholders were shown a feature at the review, and then they would find out that it may not have been what they asked for.

So the problems they were having were:

  1. Slow or no feedback from stakeholders
  2. No dedicated feature testing of new or existing features
  3. Front end automation tests that back to back would take over 60 hours, and run in parallel would run for 4 hours. (these were also fragile)
  4. No trust in the selenium tests – the tests are being fixed rather than the code.
  5. No unit tests
  6. Some business logic tests but they relied on experts being available to check them
  7. No stakeholder involvement in meetings
  8. No-one is thinking like the user


How did I approach this list?

Slow or no feedback from stakeholders:

Well this wasn’t so easy, but I tried to do a couple of things.

First of all it became clear very quickly that the business side of the company and the development side of the company actually did not know what each other did. To be able to be a representative of the user I had to understand who our users are and what they do.

Engage with the whole company:

So my first point of call was to spend time with the business, but not the managers, the actual people who use the systems from an admin POV and understand the user pains.

This would help manifold. I could understand where their frustrations may come from, and in turn the users’ frustrations and also see how the system is actually being used. In some places it wasn’t being used like the development team thought but there were workarounds in place to go around bugs. Now we didn’t even know those bugs existed.

This in turn led me to propose we talk and communicate with each other more. We set up specific projects for the internal bugs to be raised and had a dedicated team working on those, improving and maintaining the current systems rather than purely focusing on getting new features out. Which had 2 spokespeople from the business who ran teams of account managers or accountants so both sides of the system were represented. These then owned a backlog and could priorities their bug fixes and discuss them as well as progress in weekly meetings.

The important thing here was to engage with everyone across the business. Try to find out what everyone’s job role is, what do they love about their job, what isn’t going too well and why.

I did get pushbacks though when I asked the teams to forward issues to their managers which would then be logged in the dedicated project. I heard things such as “it has always been like that. I tried to tell someone before.”

We as a development team even offered to automate some data inputs but people are always wary when it comes to change.


Once we started with the engagement I tried to create regular sessions on what testing is, what development is etc.

So we learned from the business but now we needed to see if they are willing to understand what we do. We set up fun little coding dojos over lunchtimes, where we used a language called Processing and tried to illustrate how the numbers and letters create systems ( or code).

Furthermore we set up a brown bag lunch on agile testing. When I first joined I was asked if I would be writing the unit tests. This got me thinking and I tried to collaborate instead. I am no coder or automation tester but I can pair on writing those tests and give feedback.

This way I tried to illustrate what I do and I decided to make my commitments public to the team. This came about because I was constantly being asked if I would write the automation tests, such as unit and selenium tests for the devs, which wasn’t the case. I stumbled upon the Tester’s commitments from James Bach around that time and wrote my own version, covering how I provide a service, etc.

Alongside this I made suggestions what the business/stakeholders could focus on for their UAT, held a brown bag lunch about how a manual tester fits into an agile team working on bi-weekly sprints, and did some pairing with developers to understand how they work.

Consequences of change:

As much as this driving of change and engagement with the business had a positive effect – we were now on the road to better unit test coverage, understanding of testing, it also ended up backfiring a little bit, where I was starting to be seen as a quality gatekeeper, with there being a reliance on manual regression testing before a release, so testing became a bottleneck, especially as the team of developers grew and more streams of work were happening. More streams of work also meant context switching a lot from regression testing bug fixes, to new features, to new architecture.

Note to self: Do not let anyone call you QA, gatekeeper, etc when you first start somewhere and if that is not your role.

The effect of this was the thinking that we need a tester per product team to embed into each agile team, as well as dedicated product owners. A stakeholder or business person with a full time job was not going to cut it anymore if we wanted to get back up to speed and be focused.

So we wanted to work towards integrated a tester into each team, to be able to test small iterations of work frequently, and aim for full time product owners so we can reduce the feedback loop and having to spend time chasing stakeholders.

Hiring and building a team:

I was mainly involved with the hiring of the testers.

We have discussed the problem briefly and why hiring was a solution. We were trying to find tester who can integrate into the various teams and be the testing professional. As the product teams were quite different it was important to keep this in mind and not just hire 3 of the same type of tester.

For the hiring process I had a good idea of what I wanted, a good fit, an experienced self starter and not an automation tester but someone who would be a front end tester, with complimentary skills to myself. As I was keen for the devs to own the automation tests.

For the actual process we did phone interviews, and face to face interviews which included a live action testing problem. Just to see how someone would test and tackle a tasks and if they ask questions or not. How proactive are they? There are some very succinct and good resources on the ins and outs of hiring testers, I am mainly thinking of the ones by Rob Lambert if you want to have a further read and get some more ideas.

Once we had a team (I counted 2 testers as a team, but we grew to 4 in total within my first year), I wanted the team to be engaged and constantly learning about testing.

Time boxed Sprints give you the great advantage to try new techniques and experiment with testing techniques and I didn’t want anyone to feel boxed in, while having some consistency. Also each tester was working on a different product which would need different testing activities and tools anyway based on their context.

This meant we had bi-weekly knowledge sharing sessions, new features, testing techniques you name it.

I also set up monthly one to ones and tried to share a blog a week or whenever I saw a good one with the team. Furthermore we added testing related books to the library which had the nice side effect that developers would see the titles of the books and have a chat with you, so you could sell them more on the subject.

There was an especially a good session with jerry weinberg’s Perfect software- where a dev walked past and challenged me that perfect software doesn’t exist. Of course the full title is “perfect software and other illusions about software testing”.

Also being an organiser of the brighton tester meet up, I encouraged the team to attend events or even speak at them. One thing I learned from this was that not everyone wants to engage as much as I maybe do. At least not on the surface. And this is OK. Just keep doing your thing and don’t get downhearted. It can seem frustrating, like you are not getting through but I would just persevere.

We did manage to have developers attend the tester meet up and even speak about testing as well.

So what does my story tell you?

The main thing I did  was to communicate.

Find like minded people in your organisation and start sharing ideas, product knowledge, skills and experience and collaborate with them.

Start creating a library of resources and learning. This could be a physical library of books, or a wiki page with suggested reading/watching or regular events that you host inside and/or outside of the company.


Seek out people in different roles within your organisation and learn about their work. Try to understand what works for them and what does not.

But don’t forget people in the same role as you. Start pairing with other people in the same role in an effort to learn more about what they do, but also to help to build relationships.

Start socialising your improvement ideas with anyone who will listen. In my experience, planting the seed of an idea can make discussions about change easier later down the line. Get feedback on the ideas. Talk to people about how the future could be different. Listen to others.

I was passionate about what I do and tried to be positive in the light of change and when driving it.

Start gathering interesting trends about the work you’re doing – and then socialise these with the rest of the business.

Sharing is Caring


Here is my blog post about sharing at Songkick, I promised Helena I would post a month ago. Oops!

First a bit of a back story.

I joined Songkick over 6 months ago now! This seems crazy! Where does the time go?!

Time has flown by. I also cannot believe that it has been a month since Testbash Brighton. If you missed out the videos are online now here.

Anyways back to the back story:

If I think back to 6 or 7 months ago and how little I knew and how much I know now (and how much I know I don’t know) about the company and the tech, the domain, the people, job roles and responsibilities, that is an incredible amount of information to have to learn in a short time.

Luckily Songkick does a couple of awesome things that really helped with this. Here are a few ways in no particular order:


This is new and still being trailed, so it is important to give feedback but the idea and general execution was good.

So what is on-boarding at Songkick? Regardless of the job role you joined as, during the first few weeks you will be invited to presentations (mostly remote ones for me), from different people of the business. These cover many different topics, some are about the domain, certain departments or processes.

This may feel like information overload, but the most important thing to remember from on-boarding sessions, I think, is the topic and who to associate with it, so you can ask more detailed questions later and know who has the information.

These sessions were quite intense, but for me they became handy very quickly, as I knew who to contact to help me figure out who uses a certain system and who we would need to help test a scenario, or even find out what a scenario may be.

Understanding how your users (internally and externally) use the systems your team builds is such valuable information for testers.

Testing specific meetings:

Being the first, second tester in the company for a long time, this was unstructured, which has its benefits and downfalls.

Luckily the approach has been taken that if you have been asked to explain something, you write it up. So there was lots of relevant documentation on how to test certain things. These were super useful, as I did not have to rely on someone to be around, but could figure things out.

We also did mind maps of areas to have in depth sessions on, so I could learn about the other details of the system that may not be obvious. I found it interesting to make a learning plan using mind maps. It has been a nice experience though and I like the informal format of those sessions.

What was important too, was to learn about the history of certain features, to be able to look for backwards compatibility if needed.

As a downfall for an unstructured approach, you could say that, we may have missed stuff in my on-boarding process initially, but then I am not worried to ask if I come across something to be given the information instead. Sometimes that is a more rewarding experience, and also the information is more likely to stick if you had to seek it out yourself.

Dev Talk:

Every Wednesday lunchtime there is a slot reserved for the technology team to do a talk. This is accessible remotely, so anyone interested can dial in.

The topics for this can be anything, new tools, discoveries, experiments, oddities of screen sizes in Android, key takeaways from conferences, etc. Our next one is actually a Docker workshop!

These are relatively informal and more often than not inspire a nice discussion. I like these because they are generally technical and it is a good intro for me to learn some terms and then research them further.

Outcomes of experiments are always fun as well, because they are generally trying to solve a deeper tech problem which is outlined first and then a possible solution is presented. This always gets me thinking about testing the new solution and also if we are missing anything in the current one.


Show and Tell:

Show and Tell is a special thing. This for us in the UK happens on a Friday afternoon, involves the whole company, and generally some alcoholic drink. I don’t drink so I don’t care about the alcohol but it seems to be a nice tradition.

Show and Tell is open to anyone in the business but whatever you show cannot exceed 5 minutes. The format is very informal and usually is more of a demo than a presentation. The sort of stuff we see are:

  1. Developers showing improvements to a tool, process, feature.
  2. Business development may show some interesting campaign they won or lost.
  3. Support may show case a nice, angry or funny support case.
  4. Any internal tools that improved productivity.
  5. UI and UX guys may show a new concept or something they learned from research.

What I love about this, is that someone is always showing something. And you get to see what people are passionate about and that they care about their job. It also gives you an insight into problems teams have with tools or products and may give ideas on how to solve them. The other things that is great is that this is that the whole company gets involved to show something.


Breakfast Code Club:

I have not been able to go to many of these yet but they are quite fun. The idea is that something to do with code can be shown off. This does not have to be work related. It can be a side project.

For example:

  1. A game
  2. Trying to solve poker algorithm
  3. A pun generator (my fave!)
  4. Solving ciphers.

Sometimes the stuff showcased is work related and this time can be used for a code review as well.

The other selling point is that it is a nice way to mingle with colleagues you may not naturally work with and also there are pastries!


The film Breakfast Club was released 31 years ago … yep we are getting old! 🙂



Agile Testing: Frustrations can make us creative


creative space design of a restaurant

I love the fact that I have worked at a few different companies and hence have gotten to know so many awesome people.

It also has the great benefit that I still get to take part in different conversations around Agile Software Development practices and especially when the focus is on testing.

The other day I was forwarded a little article by Mountain Goat Software which focused around the fact that in an agile team, at the end of the sprint everyone tests. And some developers may not like manual testing so they will do automation testing or pair with testers to find efficiencies.

“At the end of the sprint, everyone tests.”

I am wondering a few things around this line of text. Why does everyone only test at the end of the sprint?

I know there have been many discussions that “testing” means manual testing being done by a human. But I do think that developers are often using Test Driven Design to write code and hopefully are also running the code they write to test that it does what they intended and maybe also how it does not (depending on experience, mind set, time pressures and learned habits).
Nevertheless the above quote is important for agile teams. I have experienced that as testers you can easily become a bottleneck because the developers think their part is done. Ideally they will have written the code and written automation tests as well. Now the manual testers get to test the new feature works and hasn’t broken anything.

But this leads to the problem that the developers are sitting there twirling their thumbs or starting more work, adding it to the bottleneck until the pipeline completely collapses.

So I like the fact that there was an emphasis put out that everyone should test as the team is responsible for shipping the work altogether.

I do hope though that testers and developers in a team get to test early as well, or maybe even designers or product managers, to make sure that the feedback loops is as fast as possible. The statement has the danger to be interpreted as such that testing should only happen at the end of the iteration. (I don’t think that is actually what they are saying.)

The excerpt I read actually states that the better the agile team the later the testing can occur. This seems wrong to me, but maybe I am taking it out of context and it is referring to the time needed for the whole team to be testers.


“Establishing a mindset of we’re all testers at the end, does not mean that programmers need to execute manual test scripts, which is something they’ll probably hate.”


The article went out to say that developers may dislike using manual test scripts for testing and hence maybe could focus on other things such as automation scripts.

I actually thing that it will be really beneficial for developers to do manual testing, not necessarily follow test scripts but explore the features they wrote instead.

By all means make sure your code is well tested using automation tools but you will not know if you have written the right code if you do not manually test it. You will only know that the code is written in the right way.


Frustrations can make us creative

I recently watched a video that Chris recommended on How frustrations can make us creative and it highlighted how doing something you maybe don’t like can actually result in you finding ways to make it better a lot easier than doing stuff you enjoy all the time. So developers definitely can really gain from doing some manual testing. And not just developers but hopefully the whole team.

A sort of related example of this is, that at Songkick we try and learn about what each department does and were encouraged to help the support teams. This has actually led to improvements being made to the admin systems when developers used it to help solve support cases. It is OK here to JFDI, when an improvement can really help someone.

A small example was that someone added extra information to be pulled in on one screen, so that you do not need 2 tabs open anymore to find all the information you need to close a support case. This was a huge time saving for everyone and was only achieved because a developer used the tools he created for the support team.

So I encourage everyone to test, collaborate and try something that frustrates you and see if you can make it less frustrating to do.



Don’t get stuck, try something different


view when trying a new running route I saw a double rainbow!

If you don’t know by now, 5 months ago (5 months!!!) I joined Songkick.

One of the many things that appealed, apart from working with Amy of course, was to experience another way to develop software, namely Continuous Delivery.

So this post is a bit about, not getting stuck in your job, routine, thought processes, try something different when you can or if what you are doing doesn’t feel right!

How did I get into this topic?

Songkick has had quite a few new hires in the tech team over the past few months and as part of the on-boarding there is a an intro into how we test at Songkick.

For 2016 Amy has been mixing this up by making the session super interactive and it really works.

As part of this we spoke about exploratory testing over test plans and how your emotions can drive your journey through the system when you are hunting for information and bugs.

All this “huh!?”, “oh!”, “OH!?”, “ah”, and “erm” moments can drive your test journey through the application as a tester and developer.

On the flipp-side to this is boredom. Boredom is another emotional state to avoid. Question why you are bored. Have you exhausted your testing journeys, do you need to mix it up by using different devices?

Boredom and feeling a little stuck was what drove me to try something different.

First a quick back story.

As part of a merger in early 2015 Songkick is doing some re-aligning of technologies. To keep it as vague as possible. I have been part of one of those teams working towards one platform. This has been super exciting and provided a great learning experience as I could learn about both companies technological history.

But this means we have some (or a lot of) manual regression testing we do as a team. This is generally unusual for projects there but a way of providing confidence for the team and whole business.

Now where am I going with this?

My boredom (don’t tell my team, I keep telling them that all testing is fun) came from the fact that I was regression testing something that we did have confidence in, over and over again on different devices and browsers, but it is quite a risky project so we rather test twice and in person alongside automation.

In the retrospective I was surprised how concerned everyone was that the testing was left to one person while the rest of the team tries to finish off other tasks before the release date. 

One of our team members had the great idea to block out some time and get everyone to test for an hour together.

Go with the energy.

Straight away I jumped at this and expanded on the idea. We discussed that this 1 hour session will involve all team members and we will test on different devices and browsers.

I was however not keen on providing a list of testing tasks or test plans as I wanted everyone to feel free to explore, so I created some user scenarios for everyone to have and try. They were meant as inspiration of what to test and a way of visulaisin how the software may actually be used.

 This seemed to work well, although the volume of scenarios I supplied was frightening some initially, but by emphasising that these were ideas and did not have to be ticked off we got somewhere really quickly.

Make it as easy as possible.

One major thing with testing systems can be the test data. This can be time consuming to create and manage, putting people off spending time on testing. I took this away from the team and provided them with different test data options for the various scenarios. These were the same selection of test data meaning we had a mini performance test of several users, accessing the same data. Being in ticket sales though we generally deal with short and high spikes of data which we are testing using automation. 🙂

Entice them

This can be as simple as buying jaffa cakes or bringing in some home made cookies. Always works a treat!


Trying a new recipe!


We had a focused testing session and logged several issues. None of which will block our release, thank god, but some which would have taken ages to find for one person.

Also we logged improvements on usability, as our designers and usability experts took part and got to experience the app first hand in a repetitive situation.

Overall this was a success, we got many eyes and devices to be used at the same time and it was a great team experience!

So don’t get stuck but do try something new! You never know what you may achieve. 

Thoughts: Should I stay or should I go now?


 The last Testing in the pub podcast was about leaving testing and why do testers move on or stay in the profession. I thought it was a nice exercise to think about why I left testing once and why I am back and here to stay.

Spoiler: I am not thinking about changing away from testing in the immediate future. I still feel like I have only just discovered testing as a career and profession that I enjoy and grow in.

But I did reflect a little bit on the subject and why do I stay in testing, but maybe change job relatively often and how did it come to this? Well let’s start at the beginning because I have left testing as a whole before.

The Beginning:

Straight out of uni I knew one thing and one thing only, I wanted to stay in the Brighton and Hove area. This meant getting a job.

Being bilingual and having just studied German at university I looked into jobs which would utilise my language skills and found a localisation tester job for a 3rd party games testing company.

I passed their onboarding process and started to work there. It was semi-freelance in that you had to grab as many hours as you could to survive. But I loved the experience and often found issues that weren’t just language related.

I liked the fast paced environment of working on different platforms and types of games. There were a couple of issues though, the work was fun and didn’t seem like “work”, it was slightly unstable in that you had to fight for the hours on a project and I did not see a career path.

In the company there were leads who were mostly project managers for a certain language or game but there was no progression to stay in testing. This made the job seem like a dead end to me and I didn’t look into it any further when a different language based (sales) job appeared locally.


Eventually (because I hated sales) I found games testing again. This time as a full time tester. It still just seemed like a fun job and not a career but then something happened.

  1. I was working with someone (now an amazing friend of mine) who had been a professional software tester prior to this job and pointed me in the direction of great articles and testing practices. And she just made me think, a lot! In a good way!
  2. I had an amazing QA manager who made you aspire to be like her. She was awesome, inspiring and supportive even though she was based in Canada while we were in the UK. (Still sad we never worked closer together).
  3. I became curious and started to google more about software testing and not just games and localisation testing.
  4. I won a ticket to go to a software testing conference.

This all happened within 18 months and shaped my mind for the future.

After the conference where I tried to speak to as many people as possible I realised that testing was not just what we did. There are many forms, more engaging environments and also more challenging environments and I wanted to see more.

The next steps I took were to activate my twitter account and to start posting in the Software Testing Club forum.


Leaving – with a purpose:

Why did I leave that testing job? There was no room for progression. Learning was stifled, management wasn’t great locally and it seemed like every day was full of negativity. Don’t get me wrong I loved my role (mostly) especially when it involved doing more stuff with the teams abroad (as challenging as cross time zone working can be).

Being curious about actually testing software and not doing what seemed like a glorified editor job, I applied to as many positions as Brighton and Hove had to offer and eventually got lucky.

I would like to think that my enthusiasm and involvement in the community helped a great deal in securing the job. And I would also like to think that maybe I helped to start a small testing revolution that Emma is continuing. 🙂

Leaving again!?

Unfortunately due to personal reasons and when an opportunity occurred that would solve some of my personal issues, I left that job. If I could have stayed I would have but the other opportunity was great and my personal issues meant that long term I couldn’t afford the commute to the previous job.

So sometimes we leave testing jobs for other testing jobs due to personal reasons which is also fine I think. Maybe we can see this as location being a factor and maybe also renumeration.

This next job was a bit bigger and initially maybe more than I could handle but I think I did it to the best of my ability.

I hired and managed a small team of testers within a year of starting there. This pushed me a lot and I learned a lot and engaged with the community in a totally different way. I guess initially I spoke mainly to peers who were also testers that report to someone but not managing anyone and then suddenly I was trying to find good testers and also provide a good environment for them (shame the business wasn’t quite up to that though).

Leaving again again!?

The community can be such a great place to network. Attend meet ups and just strike up conversations.

This is how  I came to leave again and end up where I am now. The challenges are completely different and I am learning a lot which was part of the appeal to move on to a new role. Also in the podcasts the guys mention that sometimes you move on to work with people you admire and respect and this was the case this time round as well.:)

So why did I leave testing jobs:

  1. No career progression
  2. No learning or development opportunities
  3. Location and renumeration (in combination with new challenges)
  4. New environments and testing challenges to explore
  5. Gaining experience
  6. No room for creativity
  7. Slow development progress
  8. Personal reasons
  9. Opportunity to try something new like managing and hiring
  10. Opportunity to work with great people from the community


Why haven’t I left testing?

  1. It is always challenging
  2. Problem solving
  3. Creativity
  4. There are inspiring individuals in the community
  5. The community
  6. Love testing and contemplating and thinking about it
  7. Love for technology
  8. Love for design and how it affects users
  9. Provides the opportunity to be a certain user (almost like acting which I wanted to do but was always too scared to)


Have you thought about your journey and why you are still in testing or not?



Thoughts: Starting a meet up

Cornwall April 2015 – Arthur’s Castle

Myself and Emma with help from loads of others have been running the Brighton tester meet up for a year now.

As we start 2016 with 2 meet ups already planned which you can find here and here, I thought I would put my thoughts on on how to start a meet up in my point of view.

January meet up – Introduction to stubbing and mocking using Wiremock

February meet up – Ghostbusting User Stories with Alan Parkinson


Whenever we post a meet up 9 times out of 10, I get asked if we can organise meet ups somewhere else too but you don’t need us, you can do it. 🙂

In my view there are some simple ingredients to starting and then being able to run a meet up.


Find a set up you like

First of all, attend some meet ups and find formats that you like that you may want to replicate.



Find out if there are local venues with wifi and projector facilities that do community events for free. A lot of them do! In Brighton the Skiff is such a venue and there are a few pubs as well. Just make sure it is not a football night.

Think about your audience size and choose a venue where people won’t be too crowded and hot and also not too far away from each other. The idea is to encourage people to chat and network.

Also do not rule out local companies. You would be surprised how many are happy to host a networking event right in their meeting rooms. All it takes is meeting someone, getting an office manager or HR contact. Maybe try their twitter or contact pages and just ask.



Hosting is also really important. Be the host or find a host. A host is a great idea because it means there is someone anyone feels they can approach. The host can do a general welcome, and introduce people. A good host can really put everyone at ease.


Food/Drink and Sponsorship

During tech talks I generally have experienced there to be beer and pizza. Be careful not to alienate your audience though. For example order veggie and meat pizzas and have soft drinks available as well.

For providing drinks and food you may want to look for sponsors especially when your audience grows past 15 people. Or ask for a donation at the end/beginning of the event.

To be able to get sponsorship, have a sales pitch ready. What do you offer in return? Any advertising, space for the company/person to do a pitch of their product?



Finding speakers can be really hard but I would suggest actually approaching and inviting people instead of putting out an ad asking for speakers. Use the 6 degrees of Kevin Bacon (since social media it is only 3) and find someone who likes to speak at events and invite them directly.


Social Media

Then find yourself a twitter account with an unusual hashtag and tweet the hell out of your meet up. Also using meet up platform really helped us be found.

I like to also scour local technology event calendars and add the meet up to those. If you don’t meet too often this is not too time consuming. And you could always double up with someone and be a co-host to split the tasks.


Have you got any questions or suggestions on how to help others start to organise events? Why not come to one of our events this year and then give us feedback, meet other testers and snoop around company offices. 🙂