Just a short post that I hope to be able to expand later. I feel that the lack of a strategic/long-term purpose affects the quality of my outputs and work.
I can be self-driven, but the problem is that the unit itself seemingly lacks purpose and mandate. Everything is based on preferences.
That lack of mandate allows our inputs to be questioned, as if we do not know what we are doing. Maybe, they are correct.
A system is required. A purpose has to be established and institutionalized.
Time to run.
Thursday, May 19, 2016
Monday, April 25, 2016
On Leadership
I am not a leader. My limited knowledge of leadership is based on my experience as a cadet officer in Reserve Officers' Training Corps (ROTC). So let me make it clear at the onset that my writing is just based on my own limited experience, and that this is more of a documentation of my learning or insight rather than a prescription on how to be one.
Leadership demands inspiration. I agree with John Maxwell's test of leadership: If nobody's behind you, you are no leader. You are just taking a walk.
Leadership does not come from mandate. It comes from respect, which usually comes from genuine care for the people you lead. If you want to lead, you have to care.
Leadership is a relationship (duh!). Leadership is not about legal authority, it's about people's trust in you.
Leaders put the needs and welfare of their people first, before one's own. Even in battle, the leader leads, not just commands.
In relation, a leader recognizes that it is best to motivate rather than command. A command is based on legal authority, a motivated action is based on a shared goal and values.
Leadership is about making tough decisions. You may consult, you may get inputs, but in the end, you have to make the call.
And in relation to that, leadership is about responsibility. Some organizations punish individuals who make wrong decisions. We cannot fault organizations for that as they have their purpose. Nonetheless, the leader has to make that choice, and take the responsibility for its outcome. The leader does not pass the buck.
The leader leads. Before a leader commands, and for me, before a leader should command, the leader does what he tells others to do. Don't expect other people to stick their necks out for something that their leader would not do.
The leader does not blame his or her own action to external forces. The choice is the leader's own.
The leader knows his goal and methods, and communicates these to his people. His people are not blind nor left alone wondering what will happen next.
Just my limited thoughts. I usually tell people I do not want to get promoted to leadership position, but I want to help people be their best.
Are these my expectations of leaders, in general? Yes. But I also know that leaders are humans.
And perhaps, that's my last. Leaders are humans. They think, they feel, they guess, and they struggle which ones of these will give him the proper input to have the best outcome... for his people, his flock.
Note: Forgive me for being not gender neutral. Leadership is not based on gender. All male pronoun references apply to all genders.
Leadership demands inspiration. I agree with John Maxwell's test of leadership: If nobody's behind you, you are no leader. You are just taking a walk.
Leadership does not come from mandate. It comes from respect, which usually comes from genuine care for the people you lead. If you want to lead, you have to care.
Leadership is a relationship (duh!). Leadership is not about legal authority, it's about people's trust in you.
Leaders put the needs and welfare of their people first, before one's own. Even in battle, the leader leads, not just commands.
In relation, a leader recognizes that it is best to motivate rather than command. A command is based on legal authority, a motivated action is based on a shared goal and values.
Leadership is about making tough decisions. You may consult, you may get inputs, but in the end, you have to make the call.
And in relation to that, leadership is about responsibility. Some organizations punish individuals who make wrong decisions. We cannot fault organizations for that as they have their purpose. Nonetheless, the leader has to make that choice, and take the responsibility for its outcome. The leader does not pass the buck.
The leader leads. Before a leader commands, and for me, before a leader should command, the leader does what he tells others to do. Don't expect other people to stick their necks out for something that their leader would not do.
The leader does not blame his or her own action to external forces. The choice is the leader's own.
The leader knows his goal and methods, and communicates these to his people. His people are not blind nor left alone wondering what will happen next.
Just my limited thoughts. I usually tell people I do not want to get promoted to leadership position, but I want to help people be their best.
Are these my expectations of leaders, in general? Yes. But I also know that leaders are humans.
And perhaps, that's my last. Leaders are humans. They think, they feel, they guess, and they struggle which ones of these will give him the proper input to have the best outcome... for his people, his flock.
Note: Forgive me for being not gender neutral. Leadership is not based on gender. All male pronoun references apply to all genders.
Saturday, April 09, 2016
Quick Updates and Random Thoughts
Web-Based Performance Management Information System
I have to abandon the Google Fusion Tables-based performance information system as it is limited. Of course, that is not the only reason. The other, and real reason is that I got to actually make my own PHP-MySQL-based system. Although it is only at its initial stage (my most important achievement is a username-password protection system that ensures no page is accessible without proper login), I feel confident that I can achieve my intended system.... although when is another question.Running and Performance Management
Running is really a good exercise. But it does not only help one in physical fitness. It also helps me in approaching personal performance management.When I run, I do not run alone. I do not run with a group, but the place I run is an ideal running area, with vehicles' speed in check, paved road, and less vehicles due to the security setup of the area.
Nonetheless, while I see other people run, I am reminded of the following to help me keep my pace, and ensure sustainability in my performance:
- Keep my own comfortable pace. Focus on the distance of the run without incurring injuries.
- Focus on my own performance. Do not compete against other runners. Other runners may have different reasons for running, which drives the way they run. I know why I run, and I will try to sustain it.
- Focus on the run. Do not think about other things. When I do, I slow down, and my mental activity increases fatigue.
- Know how to prioritize. If you want to finish a big thing, you may need to abandon or remove secondary objectives. For example, as I hope to finish a 42-kilometer run in October, I am less inclined to target a sub-2 hour 21-kilometer. It's okay for me to finish it in 2 hours and 15 minutes, just five minutes faster than my last record.
- If you want to achieve something, do not compete with someone else. Compete against your own limitations, so that you improve on the measures that you need to and not based on some else's measures.
These are just some of my thoughts on comparing performance management with running.
New Spreadsheet Function Learned
So I learned how to use spreadsheet functions INDEX and MATCH to do two-dimensional or two-factor lookup. I will write about it in my next post in Technology for Teachers blog.
Labels:
database,
FOSS,
Fusion Tables,
information system,
management,
MySQL,
performance,
PHP
Friday, March 04, 2016
Introduction to Database and Database Management
I'm thinking of organizing a brief knowledge-sharing session about database next week. I hope to share what are the opportunities in having a "real database." Below my preliminary syllabus:
Learning Outcome: At the end of this 2-hour session, participants are expected to have a working knowledge and appreciation of database, and database design and management, to help them in efficient data collection, storage, reporting, and ultimately, decision-making.
Among others, the session will allow the participant to answer the following questions and apply that knowledge to their own situation/requirements:
Methods of Instruction: Guided discussion, paper form analysis, and tool application
Logistical Requirements:
Learning Outcome: At the end of this 2-hour session, participants are expected to have a working knowledge and appreciation of database, and database design and management, to help them in efficient data collection, storage, reporting, and ultimately, decision-making.
Among others, the session will allow the participant to answer the following questions and apply that knowledge to their own situation/requirements:
- What is a database?
- What are the uses of database (aside from getting stored data)?
- How should we design databases (and why so)?
- What are the available tools and techniques in processing data in a database?
Methods of Instruction: Guided discussion, paper form analysis, and tool application
Logistical Requirements:
- Projector and laptop with internet connection and spreadsheet application
- Sample report forms for analysis
- Participants may bring their own laptop for exercises
- Use database-like applications (Microsoft Excel) on a regular basis; or
- Use matrix reports from agencies that want to reuse data.
Friday, November 13, 2015
Database Design for Non-IT People
As a member of the Quality Assurance Team and a member auditor of our Internal Audit Committee (both of which are component entities of our Quality Management System), I observed that there are a lot of offices which maintain some form of database. And that is good.
However, as someone who was trained in database systems (however, this is by no means saying that I am an expert on the subject), I also observed that their databases are mostly 'designed' to respond to only one particular concern, which is storage of data and ensuring that they can find a particular type or instance of data for each particular record.
That in itself is not a bad thing, however, I find myself wishing that they would enhance their database so that it can be more robust, more flexible, and has opportunity for scaling up and integration.
Some of the staff who thought of creating an electronic database used Excel, a powerful spreadsheet application, are conversant with advanced knowledge of the application, which means they know more than simply typing values there and using basic arithmetic formulas using absolute and relative references. However, choosing Excel, or other spreadsheet application like LibreOffice Sheets, to use as a database management system is an indication that the choice did not consider the long-term opportunities of making other management decisions using the same existing data by merely organizing the data properly.
Still, I think that advanced skills in spreadsheet applications is an indicator that they can easily understand the basic concepts of database management.
Considering, this, I really want to share what I know about database management to these people so that they can be more conversant opportunities in proper database design so that they can easily find the information and knowledge they want from the data already in their computers and files.
I might post some future articles on the matter so that they may be able to read it, in case they want to learn and we just don't have the time to do it during office hours.
However, as someone who was trained in database systems (however, this is by no means saying that I am an expert on the subject), I also observed that their databases are mostly 'designed' to respond to only one particular concern, which is storage of data and ensuring that they can find a particular type or instance of data for each particular record.
That in itself is not a bad thing, however, I find myself wishing that they would enhance their database so that it can be more robust, more flexible, and has opportunity for scaling up and integration.
Some of the staff who thought of creating an electronic database used Excel, a powerful spreadsheet application, are conversant with advanced knowledge of the application, which means they know more than simply typing values there and using basic arithmetic formulas using absolute and relative references. However, choosing Excel, or other spreadsheet application like LibreOffice Sheets, to use as a database management system is an indication that the choice did not consider the long-term opportunities of making other management decisions using the same existing data by merely organizing the data properly.
Still, I think that advanced skills in spreadsheet applications is an indicator that they can easily understand the basic concepts of database management.
Considering, this, I really want to share what I know about database management to these people so that they can be more conversant opportunities in proper database design so that they can easily find the information and knowledge they want from the data already in their computers and files.
I might post some future articles on the matter so that they may be able to read it, in case they want to learn and we just don't have the time to do it during office hours.
Subscribe to:
Posts (Atom)