diff --git a/docs/MAINTAINERS.md b/docs/MAINTAINERS.md
index dc7966676..746269a6b 100644
--- a/docs/MAINTAINERS.md
+++ b/docs/MAINTAINERS.md
@@ -8,8 +8,8 @@ If you're interested in joining the team as a maintainer, check out the [becomin
 
 ----
 
-## Technical Lead: Joel Cooklin (@jcooklin)
-While our maintainers guide Snap, the plugins, and the community forward in a positive direction, our technical lead, Joel, is the key decision maker and fearless leaders for all of us. If there is ever a debate within the project, Joel is the tiebreaker. 
+## Technical Lead: Izabella Raulin (@IzabellaRaulin)
+While our maintainers guide Snap, the plugins, and the community forward in a positive direction, our technical lead, Izabella, is the key decision maker and leader for all of us. If there is ever a debate within the project, Izabella is the tiebreaker.
 
 ## Snap Maintainers
 Below is the list of Snap Maintainers, they are largely responsible for approving pull requests and thus have the final say on coding style and implementation. 
@@ -48,4 +48,4 @@ Contacting us is easy! Use these simple tips for the most effective communicatio
 * **For a quick question:** reach out to us on [Slack](https://slack.snap-telemetry.io). You can search by GitHub handles and ping individual users, start a group conversation, and post to the Snap community. Maintainers check this regularly and will be the fastest way of contacting us.
 * **If you find a bug in the code or have a question about some code:** go ahead and [open up a GitHub issue](https://github.com/intelsdi-x/snap/issues). This will start a dialog. If you don't know how to solve the issue we will pick it up and help fix the bug. 
 * **To get a specific person's attention:** @mention them in an issue and they will get back to you.
-* **For plugin related issues:** contact the plugin's author or reach out to a maintainer.
\ No newline at end of file
+* **For plugin related issues:** contact the plugin's author or reach out to a maintainer.