You must be a ticket holder to proceed
Ticket holders must sign in to LeadDev.com with exactly the same email address as stated on your ticket.
Do you have a LeadDev.com account matching the email address on your ticket?
My email is not recognised or, having signed in, it says I do not have access to the content
Double check your ticket to make sure that you are trying to access with the correct email address (see below for where to find your ticket).
If you're sure that the ticket is correct, get in touch via Slack and we'll investigate for you
The verification email does not arrive
Check your spam and/or junk folders for the email. We know that some corporate email firewalls block our emails, and in this case you'll need to get in touch (see below) for us to move your ticket to an alternative email address.
The verification email link does not work
The links are time limited, so make sure you've tried in the last few minutes. If not, some corporate email firewalls have occasionally corrupted the verification links, and in this case you'll need to get in touch (see below) for us to move your ticket to an alternative email address.
Where can I find my ticket?
Your ticket will have been emailed to you from support@tito.io (Tito is our ticketing provider). If you don't have an email from Tito with your ticket, check with the person who made the booking originally. Otherwise, get in touch and we'll be able to help.
Getting help
The quickest way to get support is via our #help-desk channel on Slack (not a member of LeadDev Slack? join here.)
You can also email hello@leaddev.com although response times will be slower.
There are many things your team could do over the next year or two. How do you decide which of them to prioritize?
The answer should be that you are guided by your technical strategy, but often, that strategy is undocumented. It exists because how you approach challenges and what you choose to do IS your strategy. But if it isn’t written down, you may find different people have very different views about what you should be focussing on, and teams will make decisions for local reasons that may not support the needs of the whole organisation.
Documenting your strategy is important, but it’s only the first step. You need to communicate it effectively so that people can use it to make decisions. And finally, you need to track your progress: are you delivering what you need to? Is the strategy still the right one?
In this session, I’ll cover:
- What makes a good technical strategy
- How to document it
- How to use it to align different teams
- How to track progress and adapt to change
