Skip to main content

CTA Pro Tip Number 10

 

So my final tip in the 10 tip series are a couple of less technical pointers for the review board:

 

(1) Fill the judges with the confidence that if they were not able to continue on a project and you had to replace them, then you'd do a smashing job.

(2) Be slick, professional and knowledgable in your presentation. Use the 3-4 months before to board to have a solid presentation approach nailed. Know your 10-11 slides, and know exactly what you are going to say in each word. Don't just know the buzzwords but understand them as well.

(3) Don't get flustered. It is easy sometimes when we see a challenge that looks difficult to get flustered and convince our minds that we cannot solve it. Be calm, thinking calm and solution calm - you will land upon an answer.

(4) Sometimes there isn't a right or wrong answer in a key area, but make sure you can justify your solution choice. This is particularly important when making a single or multi org decision in your solution as the rest of your solution will no doubt hang on it (Role Hierarchy, Sharing especially). So choose a route wisely, and frame your jusitification and solution around it. Try not to do any last minute major changes in your solutioning as that will eat up your time and your mental sanity.

(5) Balance PPT vs Hand drawing. I discovered that I was really quick at creating PPT slides with tables and text, but quicker at drawing data models on paper - so consider what balance works for you.

 

So finally, I'd like to say a best of luck to everyone who is on this journey and wishes to continue in the future. Stay the course. The CTA is not about the badge of honour, but about the learning and knowledge journey that you underdake... What makes a great architect is one that continues to learn, grow and solution wisely for the customers...

1 comment
  1. Nov 13, 2020, 10:42 AM
    Agree with all those points, 3,4,5 especially. My first attempt I wasted half my prep time with the sample deck which already had someone else's content in (that was different to my solution) and I never recovered from the time lost. Also if you have any weaknesses you know about, get hands on experience of them rather than learning to draw the right pictures (e.g. complex sharing/TM2, Oauth complexities, multi-org, SSO etc)
0/9000