What does it take to lead when the situation demands something completely new?
In this inaugural episode, host Jennifer Tarle sits down with Rob Pakulski, a veteran in banking, finance, and technology, to discuss his extensive career journey and insights on modern leadership. Rob, a business manager for Tarle Speech and former leader at institutions like JP Morgan Chase, shares how he applied his engineering background to the world of finance, creating revolutionary operational processes [02:12].
The conversation covers how technology and the role of technologists have evolved, the nature of true innovation (not just implementing the newest thing) [12:09], and how to quickly iterate on systems after mergers and acquisitions [07:44]. Rob also provides valuable advice on team culture, what he looks for in new hires (passion and energy) [17:12], and the profound impact of having mentors who provide honest, direct feedback [22:50]. Finally, he encourages young professionals to leverage their "new person privileges" to ask for advice and build crucial relationships [27:34].
Rob pulls back the curtain on: -The pivotal difference between being a leader and being the leader needed for a specific situation. -How to successfully seek out and leverage mentorship at every stage of your career growth. -The toughest decision he had to make that ultimately unlocked his biggest career pivot.
If you're ready to stop reading management books and start doing the work, this is your next step in mastering executive leadership.
Welcome to the Business Journey Stories,
Knowledge and Lessons.
I'm Jennifer Tarle, I'm your host for today
and for our inaugural episode.
I bring you Robert Tokolsky
and Rob is a business manager for Tarle Speech.
Yes, he works with me and he is my husband.
He's also the chairman of the McCamless
Northern Allegheny Heritage and Cultural Center,
FDPC board with McCamless Township.
He has a long career in banking, finance and technology,
specializing in integrating new technologies
and processes into companies like JP Morgan Chase,
Franklin Templeton, KeyBank and Comerica Bank.
We are going to have a discussion today about his career
and we are going to touch on how technology
and the role of technologists have evolved
in banking and finance,
how to handle changing nature of work with AI
and other new technologies and most importantly,
how to stand out from the crowd.
So without further ado, let's bring in Rob Tokolsky.
Hey Rob, how are you today?
Hi, doing very well, thank you so much.
Appreciate you being here.
Yes, awesome having you.
So again, Rob is my husband.
So this is like really fun to have you here.
We usually don't have this type of discussion
at least on video.
So let's go ahead and jump into it.
So let's start with,
why don't you briefly walk me through your resume
and tell me about your journey thus far.
So real quick, just to first of all,
I just wanna say thanks for being here.
Even though I see you every day,
I love being this in the professional environment.
And so just as far as a quick overview
is I consider myself a Midwest U.S. boy.
I grew up in Ohio,
although have spent time across the country,
living in California, New York, Ohio, Illinois,
different areas now in Pennsylvania.
And my original background is in engineering.
So I ended up having an engineering degree to get started.
But then something very serendipitous happened
that on campus, a recruiter came from Comerica Bank,
which I had never with my engineering background
thought of working at a bank at the time.
And the reason was,
we had some very visionary people working at this bank
that wanted to apply technology and manufacturing processes
to a banking environment.
And that was considered very revolutionary
and new at the time.
And it ended up being a great choice,
going to go work at Comerica Bank
and getting into the banking world.
It was just when a lot of the internet capabilities
just started coming online in the world,
and it had a profound impact
on the banking and finance areas.
And the technology group, when I joined,
was not something that it was the big, hot, sexy thing
that you see now as far as technology.
It was more seen as something that you had to do,
but not something that was front and center.
So very quickly then after starting at Comerica Bank,
I did then get a master's in business administration,
and then started doing different roles,
incorporating technology
and different operational processes
into the banking and finance world.
So one thing has led to another.
I've worked at different financial organizations.
The major one for the last 20 years that I worked at
was J.P. Morgan Chase,
in that I started to work at a regional bank
that merged with J.P. Morgan to become J.P. Morgan Chase,
which is the largest bank in the U.S.,
and ended up being a global powerhouse.
But that happened because they were able
to put together a lot of technology and technology systems,
to be able to have a lot of discipline around it,
and be able to have a consistent culture
to be able to implement this technology.
And I do give credit to the leadership at J.P. Morgan
saying how important technology is
and how much they're going to invest in it.
So I've been able to ride this wave of technology innovation
and technology change for a very long time
to see massive trends and changes.
And it's been an extremely exciting time
to be able to be in technology,
and also to see how it changes banking and finance.
So I have had the best of careers,
and it's just a lot of fun.
So why don't you tell me, first off,
what is the biggest thing that you've learned
that you did not expect
when you first started working in technology?
Probably the biggest thing that I have learned
is there's way more opportunity
than you can possibly imagine,
that technology impacts everything.
And even though you do have a lot of personal relationships
that run a lot of things,
the advent of technology can be used in almost any regard,
and to not limit yourself on what it can be used for.
So that was the biggest thing I've learned is this.
You may think that you may not have a certain capability
because you don't know a certain business,
but you can get to know that business fairly quickly
with the right people.
And then you'd be surprised the types of opportunities
that may have not been explored.
So to me, that's the biggest thing I've learned
is the opportunity set is far larger
than you would possibly imagine,
especially if you have a good basis
and understanding of technology,
some of the technology processes,
as well as just technology terminology, if nothing else.
The opportunities are just tremendous.
So you mentioned that you're an engineer by training,
and then you started in banking.
How did you even know that was a career path?
Because it doesn't seem like the two are related.
And I have to give a shout out
to the people who hired me originally out of college,
because I saw the same thing.
I was like, how does this apply to banking?
I'm using technology and operational processes,
mathematical modeling that was more meant for manufacturing.
But the approach was really we're like manufacturing,
except we're manufacturing zeros and ones in information,
and we're moving information around.
And so instead of moving a widget
down an assembly line or someplace,
we're moving information.
And you can apply a lot of the exact same disciplines
and exact same approaches,
but you can actually even do it faster
because you're not having a physical widget
or a physical item that you're creating.
So it was a little, when I first started,
it was very unusual at the time.
No longer is that unusual, no longer.
It has become the rule now.
So a lot of people are looking for that engineering talent,
that mathematical talent,
to be able to apply to all different kinds of processes.
But at the time it was fairly revolutionary
to be able to say, let's use this exact same approach,
but within a finance or banking construct,
but now extremely common.
So interesting, okay.
Okay, so you talked about problem solving.
What are some of the problems that you had to solve
at a bank using your engineering background?
A very common problem would be
when you have a merger acquisition
that you have multiple different systems involved
to be able to keep contact with your customers
and also your internal systems.
Trying to figure out which systems to use,
how to be able to migrate one to the other,
and then finally,
actually being able to do the implementation.
All those three things.
The first one, choosing which system to use
tends to be more on, you do have data around it,
but then you also want to make a decision very quickly.
So there's a lot of leadership involved in that
to get leadership aligned.
Because otherwise, if you have two different organizations
or three different or four different merging together,
of course, each will try to figure out
can they use their own systems
as opposed to going to somebody else's or a new one.
So having leadership involved
did not only go through the mathematical approach
of pros and cons,
but then the leadership to be able to break through
and say, we're going in this direction.
And then figuring out the plan
of how to do that technically is another skillset.
And then thirdly, the actual implementation
of making sure you can do this.
It was a very common thing,
especially as a lot of these companies grew by acquisition,
that you had to take multiple systems
that have been in place for decades sometimes,
and then combine them to create something
that was seamless for the customer was daunting at times.
But it also was work that had to be done
because if you didn't do it and put it off,
it would only get worse and everything would just,
you'd have 12 different systems
that didn't talk to each other, which was a huge problem.
So a lot of people who didn't want to deal
with that problem immediately, the problem got worse.
So even though it was a lot of work,
it was way better to just address the problem,
get it done right out of the gates,
right when you can, as fast as you can,
and move as quickly as you can
to be able to get onto an integrated systems
that all work together.
And the more you can get some alignment
across all different business processes,
the easier it was for everybody.
So you talked about making things easier for everyone.
What differentiates a team that can do that,
that can make things easier and better for everyone?
What makes a team special?
And to me, it's the major focus on the result
that you want to get clear alignment.
And I'll give this to the leadership group,
that the leadership group has got to be very clear
on what is the end result we expect and when.
So making sure that we're very aligned
on what is the end result.
And usually that comes with a deadline of,
I want this done by this timeframe.
So usually that helps focus everybody
to be able to get that done as this is what we want.
And otherwise this is going to go on forever
if you keep arguing.
So we're going to put strict deadlines on things
to make sure we make the decisions we have to
as fast as we can,
but still give the appropriate amount of time to do so.
And then secondly, having the right skill sets
and of people who not only can understand
the business aspect of it,
but also understand the technical implications
on how you're going to support these systems going forward.
So it's not just a short-term decision,
but a long-term one on how are you going to continue
to support these things.
And then finally to have good follow-up
once you do implement so that you can make adjustments
because very rarely is everything exactly perfect.
It's going to be iterative
and you're usually going to have a version 1.0 of things.
And then you're going to have to very quickly adjust
and very quick.
So a lot of people think you're just going to do this one time
flip the switch and everything's perfect.
It usually doesn't work like that
because it would take too long to be able to do that.
So usually you get a version of 1.0 out,
put guardrails around it, make the improvements,
then do a version 2.0, make improvements
and iterate very quickly.
So having a good team that can adjust quickly
and be able to deal with problems that come up
are very key in all of this.
So that sounds like a very risky move,
trying to move quickly.
You probably upset some people
by implementing certain things that people didn't want
or getting rid of certain processes or programs.
So I hear a lot of people talking about innovation
and risk in business.
Can you tell me a little bit about that?
Like what is true innovation in your experience
as opposed to just implementing the newest
and the latest and the greatest?
Yeah, actually doing the actual implementation
of something new is usually the easiest part.
It's getting alignment to actually do it
is the bigger challenge.
In fact, always a joke around the industry tends to be,
well, I got final approval.
Yeah, once I implemented something and it was successful,
then everybody approved it.
So that's always a big joke.
It's like, yeah, once it's implemented and successful,
whoo, yeah, I was always behind you.
To me, the more difficult thing
is to be able to push for something new
when not everybody sees it just yet.
To me, that is the hard part.
When there's something that's obvious,
to me, I'm not saying that's as innovative,
but to be able to push for something
that you think is going to change things
and that will take a little bit of risk is innovation.
So you're gonna be out there.
We always say innovation,
a lot of people will think that it feels like all hearts
and roses and parades from the very beginning.
It is not like that.
So at the very beginning, a lot of times folks are like,
why would we ever even think about doing this?
You have to be able to create the case
and create the momentum to be able to do it.
And to me, that is true innovation,
to be able to push through
when not every single person is in alignment
and continue to try to do something new.
That's the difficult part, in my opinion.
And then knowing as well
that you're going to fix things as you go along as well.
Things may not be 100% perfect.
As long as everybody understands that,
you have guardrails around how to handle that.
And you understand this is version 1.0.
This is what this means.
So to make sure you got the right expectation
of what that is.
And then very quickly have the capabilities
to be able to adjust.
So that ability to adjust and move quickly
is something that is a hallmark
of innovative organizations.
The ones that are not as innovative
tend to make sure and move more slowly
and will not iterate as quickly.
So usually the faster, more innovative organizations,
they may be through 10 iterations of something
before the slower moving organization does it one time.
So of course, the group that's done it 10 times
will be much more aligned with the market
because they've adjusted 10 times already
in the time somebody else did it once.
So that being able to move very quickly
is a hallmark of innovation,
to be able to move quickly
and to recognize that you're going to have to adjust
and just understand that going in
and making sure people understand
you're going to adjust and adjust really fast
as you go along.
Okay, so let's move into team culture and leadership.
What is your professional philosophy
on the culture of a company?
What do you think makes a good company or team culture?
To me, the biggest thing in culture
is it comes down from the top,
in my opinion, as far as how the leaders treat everybody
and how they treat the business itself.
And so that kind of sets the tone.
So how you interact on a daily basis, that is the culture.
So how you interact, not only with the employees,
but also with customers.
That's the culture of how we treat our customers
and how we treat each other.
So usually if you spend time with the leaders
and with customers,
you'll figure out the culture really quickly.
No matter what's written on a piece of paper,
how people actually treat each other
and what they see as important,
what actually gets done is the culture.
That's what gets done.
And so if somebody says,
oh yeah, we're all about innovation,
but oh, it's going to take us two years to make a decision.
Well, your culture is one that takes two years
to make a decision.
No matter what you state in your mission or your goals,
how you act really is the most important thing.
And everybody pays attention to that.
Customers pay attention to that.
Employees will know that.
Everyone will know what the real culture is
versus what the stated culture is.
And to me, that's always the big one
to know what is the real culture.
You really don't know in an organization
until you start working with it.
And then you see how people treat each other,
what gets rewarded, what doesn't.
And then you get to know
what is the real culture of the organization.
So I know everyone's going to want to work with you.
You're great to work with.
So what do you look for in a new hire
and what would impress you maybe on someone's resume?
And so I get asked this a lot
as far as what types of technical skills
should a person have.
And those are very important, of course,
whether you should know Python or .NET or Java
or something like that, some programming codes.
Very nice to be able to have as table stakes.
But really what's hard to recreate
is your passion and your energy.
So to be able to have passion for the job,
that you really want to do this
and you are going to do whatever you need to do
to make this right.
And you just love it.
That is infectious.
So you definitely want people who have a passion
for what the job is going to be
and the ability to figure out whatever they need to.
Of course, you need to have some base skills,
but bringing in that passion and energy
is extremely important
because you can always learn the technical skills
at some point.
It's hard to teach passion and energy
and curiosity and enthusiasm.
That enthusiasm is just infectious.
Everybody wants that.
Everybody wants to be able to have that
in their organization.
And then the third thing I would mention
is that you want somebody
who really thinks they can absolutely get the job done.
They will figure it out.
So I'll be surprised a lot when you do talk to some people,
they never actually ask for the job.
You're like, okay, do you want to do this job?
A lot of times, you'd be surprised.
A lot of people are like, okay, am I done now?
But then you've got people saying,
just to let you know, can I have the job?
I really want this job
because I think I'm going to be able to do it.
I know I'm going to be able to do a very good job at this.
But the biggest thing I always mention to people
is the enthusiasm and energy that you bring
is really infectious
and something that everybody wants on their team.
Yeah, that is such a great takeaway,
which is be bold, ask for the job.
I love that.
That's a good, simple, but very effective tip.
Okay, let's flip the script.
What makes a good boss?
What makes a good, I'd say boss more than leader.
What makes a good boss?
So to me,
I'd answer this question a little bit differently.
It depends on the situation,
so what the boss needs to do.
So to me, the best boss adjusts based on the situation.
So for instance, if you have a major crisis going on,
your behaviors are going to be a little different
than if you're just doing some major strategic planning
and you're really thinking deeply.
So having a boss that adjusts to what the situation is
is the best, in my opinion.
So when there's a big crisis,
you want a captain in a storm
and there's going to be some barking out of commands
because that has to happen.
You're in a crisis situation,
as opposed to when you're in something
that you're looking to be a little more freewheeling
and you got some time to do brainstorming and all that,
you're going to adjust a little differently.
So to me, a boss is somebody
that just recognizes the situation
and then can adjust their leadership behaviors
based on that situation.
Because sometimes it's good to be set deadlines,
other times it's good to just sit back and listen
and let people run a little bit.
That's number one.
Number two is a boss who is not afraid of hiring people
even smarter than themselves.
That is the key to it all.
Like you run really smart people, really driven people,
people who can get the job done without micromanagement.
So that's the second thing I'd mention
is just you bet on people.
So knowing and having a good boss that bets on people
is their number one thing.
And they do realize that they have to have good people
to be able to make this happen or else they won't succeed.
And every once in a while I'll see some bosses
who are like, oh, this person,
they know even more than me.
I don't know if I want them, they might compete with me.
A good boss will be like, absolutely,
I want every single team member on my team
to be even better than me.
Like, absolutely.
That would be ideal if I could have that.
That's the second thing I've mentioned.
And so I'd go with the situational leadership,
being able to adjust based on what the situation is.
And secondly, you always bet on your people.
Like that is, you wanna be able to do that.
So you're gonna spend the time appropriate
on being able to choose the appropriate people
and to be able to take action
if somebody turns out to be not a good fit.
So you're gonna have to do both of those things.
It would take a lot of time and energy.
So seeing a boss that invests a lot of their time
and energy into managing people
and being able to lead people is something I look for.
Awesome.
So flexibility and situational in terms of situations
so that you can be the best leader
that the situation requires and confidence in your people.
But I think even bigger than that, a little humility,
knowing that you may not know everything.
So that is great to think about.
I know you've had a few really key mentors in your life
and you take mentoring very seriously,
I think because of that.
So who has been your most influential professional mentor
and what is one key thing you've learned from that person?
So to me, it's an easy one.
So there's two people I would mention.
There's one, they both worked
in different banking organizations
and they both helped me out tremendously
in being able to push me and be able to understand
I am capable of far more than I ever thought possible.
And those two people are Mike Fischbach and Gary Didier.
And they were extremely good mentors
who I still go to to this day and get advice,
even though we haven't worked together in years,
we haven't, but I very much trust their advice.
And they were not afraid to be extremely honest with me
when I was not doing a good job or I could do better,
that they would very objectively tell me that.
And that stung at the time,
but it ended up being the absolute best thing I needed
to be able to propel me into the next level
because I then had to internalize that
and finally I had to admit, you know what?
They're right, they're right.
Nobody else is telling me this, but they are,
because I think the bottom line is they care about me
and they think that I can do better.
So they, by being very direct with me,
again, not in an insulting manner,
just being very matter of fact, direct about it.
It's like, you can do better at this and here's why,
and here's what you could do.
And then of course, assisting with getting better.
The mentoring aspect, everybody asks me,
what's the number one thing you would look for in,
especially if you're a new hire?
And I said, the number one thing you look for
is can you get a good mentor?
Because that can be the difference
no matter what industry you're in.
If you have somebody who takes an interest in you
and takes a view that they're there to help you,
that is invaluable.
You definitely want that.
So lean into somebody that is going to help you
and they will point out areas you have for improvement.
And really take those to heart.
Now that is something that I really appreciated.
I don't know where I would be without it
because no one would point out,
I didn't know I had these things to work on
until they were pointed out.
Then I'm like, oh, this is,
once I then internalized it and said the right,
then it was just a matter of putting together a plan
to address it and to be able to improve myself.
And so I would absolutely encourage anyone
to either get a mentor or be a mentor.
Being a mentor, I have found out, is a real challenge
because you have to be very direct with folks
of what they're doing well and what they could do better.
And that is a difficult thing to do,
to be a good mentor.
It's extremely difficult.
So I do give a big shout out to folks who do that
because it is a very difficult role to take on,
but it has such long-term implications
and long-term ramifications that I would recommend folks
to try to do that if they can.
Any advice on the person who is getting the feedback?
How can you learn how to take that feedback
and not take it personally?
I wish I could tell you that I was perfect at this,
but I am not.
So it's a very human thing to be able to take the feedback
and then to have it sting a little bit.
I mean, that just, that happens.
I do think, though, being able to take the time
to really think it through objectively,
I call it drain out the emotion
because there's emotion involved,
but drain that out and just say, is this objectively true?
Sometimes you get feedback and it's not.
And if you can say it's objectively not,
then you move on, that's fine.
But I do think being able to drain emotion out of it
and then say, okay, is this true?
So let's drain everything, all the emotion,
is this objectively true?
If so, then how difficult would this be to address it?
And usually once you get it down to that,
it's not as big and scary or it doesn't sting as much.
It's just a problem to be solved.
It's like, okay, well, this is an opportunity
or a problem to be solved.
It starts out as you're, it's a problem,
but then it becomes an opportunity
and how you can build it from there.
And so I do think that's the biggest thing I tell folks
is take time, drain the emotion out,
and then just think through objectively,
is this something that's true?
And then if so, you're very thankful
that you got that information
because now you can do something about it.
Yeah.
Yeah, I think that's really great advice
to be thankful that you've gotten that information.
It is hard to hear feedback,
so that's a really good actionable tip.
Okay, so what is one practical piece of advice
you'd like to give someone who's just starting their career
other than get a good mentor?
What can that person do,
even if they don't have someone at work
that they can go to?
I always call it, you've got some young person
or new person privileges,
and you just don't know you have them,
which means you can go to almost anybody
and say, I would love to get your help on this
or get your point of view or get your assistance.
You would be shocked how many people say,
I'd love to help you.
Like, you would be surprised if you just asked for it.
You have this, especially new person or young person
or just starting out person privilege
that once you get to be a little bit older,
you don't have it as much anymore,
but you got getting started, people love to help you.
And it's a compliment to ask somebody for their help.
So for goodness sake, ask, use it.
Use that privilege card that you have to say,
I want your advice.
I would love to get your point of view.
Worst they can say is, no, I don't have time right now.
Don't be insulted by it.
Who's insulted by somebody saying,
I think so much of you that I want your advice.
Everybody loves knowing that.
Everybody loves it.
It's like, yeah, even if you don't have time right now,
just being asked usually, I mean, that's a compliment.
Why not use it?
People usually don't do it because they're like,
oh, I just don't feel, you know, little old me.
You know, they don't know me.
I'm like, what have you got to lose?
You really don't have much to lose.
At a minimum, they'll think you're a go-getter
or that who's just trying new things.
And it's really, I've never had it be a bad thing
when I get a request like that.
I never think, oh, this is horrible.
Who is this person reaching out to me?
I'm always like, oh, okay, that's nice.
I may not have time to do that now.
I may not be able to,
but that's pretty nice to be able to reach out.
So the biggest piece of advice I give to people
is you have more capability than you think
to be able to reach out to people.
And decisions are made logically,
but they're also made relationally.
So you need to be able to create relationships with people.
So do something to not only build your skillset,
but also build your relationships.
Yeah, I think that is huge
and very important, relationships rule the world.
Okay, on that note, we're going to close out here.
And I have one final question.
Reflecting back on everyone who's helped you
to get here to this point in your career,
what is one of the most generous or kind acts
that someone has done for you?
Like a piece of advice, a connection, a helping hand
that has changed the trajectory of your career?
That's a very good question.
And I do think I am going to go back to the nicest thing
that anybody did for me were my mentors
when they told me things that I was not doing well.
And it sounds like, wow,
and when I first got this feedback, I was like, wow,
I was not pleased with these, these are not nice people.
But then I thought about it, I go,
actually, they're the nicest people
because others wouldn't care enough
to tell me the truth of what was happening
because it was difficult.
So to me, I always give that to people
who gave me the direct feedback
with the right intent to be able to assist me
in being able to become better.
Because that is the nicest thing you can do for somebody
is to tell them where they can improve.
And it's difficult because you usually don't get
a whole lot of positive feedback immediately.
You do get it eventually.
But that's something I would mention,
which again, comes along with mentoring,
having a good mentor and being a good mentor yourself.
All right, Rob Mikulski, thank you so much.
Best business partner, husband and dad of the year.
So thank you, thank you, thank you.
Join us back here next week, everyone,
for another interesting conversation on careers.
Take care.
See you, Rob.
Thank you.